New environments on the VIP Platform are provisioned with a convenience domain. The convenience domain is a subdomain of either
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.
- 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.txtoutput intended to prevent search engines from indexing content.
- Sub-subdomains of the convenience domain are not supported.
All convenience subdomains of
- Are protected by DNS Security Extensions (DNSSEC) from threats such as DNS spoofing and cache poisoning.
- Support IPv6. The IPv6
AAAArecord value for a convenience domain can be retrieved with the terminal command:
Because non-production environments are not intended to be publicly accessible, they can always use the
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, or the network site launch tool.
Last updated: February 16, 2024