Skip to main content
A check that does not find the token never stops at “not verified”. It names one of the thirteen codes below, and the cause and fix sentences on this page are the exact strings the API returns in diagnosis — they are generated from the same function the product renders. Every claim on this page is diagnosed against acme.com, whose token is ownsi_v1_9f3a2c8d1e4b7a6053c21f8e4d7b0a95. Yours will read your own domain and your own token.

domain_appended

Your panel appended the domain to what you typed, so the record landed on _ownsi-challenge.acme.com.acme.com instead of _ownsi-challenge.acme.com. What to do. Put only _ownsi-challenge in the Host field — the panel adds acme.com for you.

record_at_apex

The token is on acme.com itself, not on _ownsi-challenge.acme.com. What to do. Move the record to the _ownsi-challenge host and leave the records on acme.com alone.

foreign_token

_ownsi-challenge.acme.com already carries an ownsi token, and it is not the one issued for this claim. What to do. Replace its value with ownsi_v1_9f3a2c8d1e4b7a6053c21f8e4d7b0a95.

expired_token

_ownsi-challenge.acme.com carries the token from an earlier claim of yours, and that claim has ended. What to do. Change its value to ownsi_v1_9f3a2c8d1e4b7a6053c21f8e4d7b0a95. The record is already in the right place, so this is one edit rather than a new record.

value_formatted

The value at _ownsi-challenge.acme.com is not exactly the token: your panel wrapped or padded what you pasted. What to do. Set it to exactly ownsi_v1_9f3a2c8d1e4b7a6053c21f8e4d7b0a95, with no quotes and no surrounding spaces.

no_matching_record

_ownsi-challenge.acme.com carries 2 TXT records, and none of them holds your token. What to do. Add the token as one more TXT record on that host, or correct the one meant to carry it.

cname_conflict

_ownsi-challenge.acme.com is a CNAME pointing at acme.pages.dev, and a name that holds a CNAME can hold nothing else (RFC 1034). What to do. Remove the CNAME on _ownsi-challenge, then create the TXT record.

record_absent

Nothing exists at _ownsi-challenge.acme.com — the record was never created, or it was saved under a different name. What to do. Create a TXT record on _ownsi-challenge with the value ownsi_v1_9f3a2c8d1e4b7a6053c21f8e4d7b0a95.

record_on_www

The token is on _ownsi-challenge.www.acme.com; the proof reads _ownsi-challenge.acme.com, without the www. What to do. Create the record on _ownsi-challenge at acme.com, and remove the one under www.

not_published

dana.ns.cloudflare.com and rick.ns.cloudflare.com answer for acme.com and do not have the record, so nothing is spreading yet. What to do. Reopen the record in your panel and confirm it saved — some panels hold zone changes in a draft until you publish them.

negative_cache

Your nameservers have the record; the public resolvers are still holding the “does not exist” they cached before you created it. What to do. Nothing to do — that memory expires in about 4 minutes, and ownsi rechecks on its own.

servfail

cloudflare and quad9 answered SERVFAIL for _ownsi-challenge.acme.com, which means the zone fails to validate rather than that the record is missing. What to do. Check DNSSEC at your provider — while the signatures are broken, no record in acme.com can be read.

lame_delegation

acme.com is delegated to ns1.oldhost.example and ns2.oldhost.example, and none of them answered. What to do. This is a delegation problem at your provider, not a problem with the record — the nameservers acme.com points at are not serving the zone.