Domain verification isn't working

This page covers why a domain stays Pending or stops being verified. Every problem comes down to the TXT record Cloud looks for: _zymlabs-verify. plus your domain, with the value Cloud gives you.

Cloud hasn't found the record yetCopy Anchor Link

Cause. A new DNS record can take up to an hour to be visible.

Fix. Wait, then choose Check now. Cloud keeps checking on its own for 7 days.

The record is on the wrong nameCopy Anchor Link

Cause. Some DNS providers add your domain to the name for you, so _zymlabs-verify.acme.com becomes _zymlabs-verify.acme.com.acme.com.

Fix. Enter only _zymlabs-verify as the name in those providers. Cloud's DNS instructions show how to check the record yourself.

Cloud found a different valueCopy Anchor Link

Cause. The record's value doesn't match, often because of a copied space or quote, or a token from another organization.

Fix. Copy the value from Cloud again, paste it exactly, then choose Check now.

Another organization verified it firstCopy Anchor Link

Cause. A domain belongs to one organization, the first to prove it.

Fix. If that organization is yours, verify it there. If it's a mistake, contact support.

Cloud stopped checkingCopy Anchor Link

Cause. It didn't find the record within 7 days.

Fix. Add the record, then choose Check again.

A verified domain shows Check failingCopy Anchor Link

Cause. Cloud's daily check can't find the record any more: someone removed it, or your DNS moved.

Fix. Put it back by the date Cloud shows. After 7 days without it, the domain stops being verified and its single sign-on connections stop working.

What's nextCopy Anchor Link

• Verify a domain: the full steps.
• How single sign-on works: what a verified domain makes possible.