Title: Convenience domain
Author: WordPress VIP Documentation
Published: September 8, 2020
Last modified: October 16, 2025

---

 1. [Domains](https://docs.wpvip.com/domains/)
 2. Convenience domain

#  Convenience domain

New environments on the VIP Platform are provisioned with a convenience domain. 
The convenience domain is a subdomain of either `.go-vip.net` or `.go-vip.co` (e.
g. `example.go-vip.net`).

Convenience domains are intended for environments to use during initial development
and to facilitate pre-launch tasks. VIP does not allow [sites on a production environment to launch](https://docs.wpvip.com/launched/)
with the convenience domain. For a site on production to be publicly accessible,
it must be launched with a [custom domain](https://docs.wpvip.com/map-a-domain/)(
e.g. `example.com`).

 * Convenience domains are covered by a wildcard TLS certificate.
 * Environments using a convenience domain are set to the [whole-site HTTPS](https://docs.wpvip.com/domains-tls/tls/#h-https-redirection),
   with all HTTP traffic being redirected to HTTPS; this cannot be changed.
 * WordPress environments that are accessible at a convenience domain have a hard-
   coded [`/robots.txt` output intended to prevent search engines from indexing content](https://docs.wpvip.com/modify-the-robots-txt-file/).
 * Sub-subdomains of the convenience domain are not supported.

All convenience subdomains of `.go-vip.net`:

 * Are protected by [DNS Security Extensions (DNSSEC)](https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)
   from threats such as DNS spoofing and cache poisoning.
 * Support IPv6. The IPv6 `AAAA` record value for a convenience domain can be retrieved
   with the terminal command: `host <convenience_domain>`.

## Non-production environments

Because non-production environments are not intended to be publicly accessible, 
they can always use the `go-vip.net` or `go-vip.co` convenience domain assigned 
to them.

If desired, the convenience domain of a non-production environment can be replaced
with a custom domain (e.g. `develop.example.com`). The convenience domain for an
environment can be replaced with a custom domain by using [the single site launch tool](https://docs.wpvip.com/launch-a-site/begin-a-single-site-launch/),
or [the network site launch tool](https://docs.wpvip.com/launch-a-site/begin-a-multisite-launch/).

Last updated: October 16, 2025