Convenience domain

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

• Convenience domains are covered by a wildcard TLS certificate.
• Environments using a convenience domain are set to the whole-site HTTPS, 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.
• Sub-subdomains of the convenience domain are not supported.

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 with the convenience domain. For a site on production to be publicly accessible, it must be launched with a custom domain (e.g. example.com).

Non-production environments on the VIP Platform can always use the go-vip.net or go-vip.co convenience domain assigned to them. However, there is the option to replace the convenience domain of a non-production environment 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, or the network site launch tool.