Named Graph
Workspaces

Verified Domains

A verified domain enables additional features that are intended for publishers and their content.

Verification Methods

To verify you have control over a domain (or subdomain), we provide a generated token that you must publish using one of several methods. The tokens are not considered secret, but are unique to your domain and workspace being verified. We support the following methods.

Once verified, the token must remain available for us to periodically confirm that you still maintain control over the domain. If repeated verifications are unsuccessful, the domain will become unverified and lose access to any domain-specific features. After 6 weeks of failed verifications, domains are removed from their workspaces and a new verification process must be started.

DNS Record (CNAME)

This method requires accessing your domain's DNS settings and creating a CNAME record for a label under your domain. We provide and recommend the following when managing your DNS settings.

  • Name is a generated subdomain for the CNAME record.
  • Target is one of our managed verification domains.
  • We recommend a TTL of 1 hour or your zone's default TTL.
  • CNAME flattening features are not supported and must be disabled for these verification records.
  • If the record is removed, the domain will lose its verified status.

DNS Record (TXT)

This method requires accessing your domain's DNS settings and creating a TXT record for your domain. We provide and recommend the following when managing your DNS settings.

  • Name is the domain name for the TXT record.
  • Content is a generated token for the record data. No other content should be returned.
  • We recommend a TTL of 1 hour or your zone's default TTL.
  • Unrelated TXT records for the same domain name will be ignored.
  • If the record is removed, the domain will lose its verified status.

HTTPS Text File

This method requires accessing the file system of your domain's web server and creating a plain text file. We provide and recommend the following when editing your site contents.

  • Path is the text file name expected from your document root.
  • Content is the data expected from the text file. No other content should be returned.
  • HTTPS is required and certificates must be signed by a trusted certificate authority.
  • The server must respond with a 200 OK status and a plain/text content type.
  • Redirects are not recommended and must always land on the original domain name.
  • If the file is removed or response is misconfigured, the domain will lose its verified status.

HTTPS HTML Meta

This method requires accessing the home page for your domain and inserting a <meta/> tag. We provide and recommend the following when editing your site contents.

  • HTML is the generated tag which must be inserted into the first head tag of your home page.
  • HTTPS is required and certificates must be signed by a trusted certificate authority.
  • The server must respond with a 200 OK status and an HTML-related content type.
  • Redirects are not recommended and must always land on the original domain name.
  • The meta tag must be before any body tag and within the first 16 KiB of the document.
  • The use of JavaScript and other dynamic, client-side features are not supported.
  • If the tag is removed or response is misconfigured, the domain will lose its verified status.

Common Errors