Operational Status: [Status] is a DNS (Domain Name System) service that, when queried with a hostname with an embedded IP address, returns that IP Address. It was inspired by and uses much of the code of, which was created by Sam Stephenson.

Here are some examples:

Hostname / URL IP Address Notes dot separators dash separators, website mirror (IPv4) subdomain subdomain + dashes embedded, website mirror (IPv4)
– ::1 IPv6 — always use dashes 2a01:4f8:c17:b8f::2 website mirror (IPv6)

Branding / White Label / Custom Domains can be used to brand your own site (you don’t need to use the domain). For example, say you own the domain “”, and you want your subdomain, “” to have features. To accomplish this, set the following four DNS servers as NS records for the subdomain “”

hostname IP address Location USA USA Singapore

Let’s test it from the command line using dig:

      dig +short

Yields, hopefully: [connection timed out]

TLS (Transport Layer Security)

If you have a wildcard certificate for your subdomain, you may install it on your machines for TLS-verified connections.

When using a TLS wildcard certificate in conjunction with your branded style subdomain, you must use dashes not dots as separators. For example, if you have the TLS certificate for *, you could browse to but not

For a real-world example of a TLS wildcard cert and domain, browse

Pivotal employees can download the * TLS private key here.


[Status] A status of “build failing” rarely means the system is failing. It’s more often an indication that when the servers were last checked (currently every six hours), the CI (continuous integration) server had difficulty reaching one of the four nameservers. That’s normal. [connection timed out]

[connection timed out]

DNS runs over UDP which has no guaranteed delivery, and it’s not uncommon for the packets to get lost in transmission. DNS clients are programmed to seamlessly query a different server when that happens. That’s why DNS, by fiat, requires at least two nameservers (for redundancy). From IETF (Internet Engineering Task Force) RFC (Request for Comment) 1034:

A given zone will be available from several name servers to insure its availability in spite of host or communication link failure. By administrative fiat, we require every zone to be available on at least two servers, and many zones have more redundancy than that.