docsUrl on it points at the anchor on this page.
code. It is an identifier and will not be reworded. message is written for a person and
may change.
These are transport errors — the request could not be answered. They are a different thing
from a diagnosis, which is a successful
200 telling you what is wrong
with a DNS record.invalid_domain
400. What you sent is not a domain name that can be read or claimed — empty, not a hostname, or longer than 253 characters. Retrying does not help. Themessage says which of the three it was.
no_delegation
404. The name resolves to no nameservers at all. Usually the domain is not registered, or it was registered minutes ago and the registry has not published the delegation yet. Retrying does not help until the registration goes through.unresolvable
502. ownsi could not reach DNS to read the zone. This is ours, not yours.Safe to retry, with a backoff.
unauthenticated
401. No valid session on the request. Everything under/api/domains, /api/claims and
/api/verifications needs one; see Authentication.
Retrying the same request does not help. Sign in and retry.
already_claimed
409. The domain already has a claim open on your account, with the token it was issued. This is not a conflict with another account — that is coexistence and it is not an error. Use the claim you already have. The token on it is the one that will verify.claim_ended
409. The claim has ended — proved, expired or canceled — and an ended claim takes no action. Its token is no longer accepted, so there is nothing to re-check. Claim the domain again. That opens a new claim with a new token, and the ended one stays as history.domain_archived
409. The domain is archived, so it is off your list: it opens no new claim and publishes no new proof link. Archiving retracts no proof — the claims it carried keep their state and their dates, and every link it ever published is still listed — but the links themselves were revoked when it was archived. Put the domain back on the list —POST /api/domains/{id}/unarchive — and act from there. The old
slugs do not come back.
domain_not_found
404. No domain with that id belongs to your account. The same code is returned whether the domain does not exist or belongs to someone else, deliberately — an id lookup should not confirm that someone else’s domain exists.claim_not_found
404. No claim with that id belongs to your account. As withdomain_not_found, the same code
comes back whether the claim does not exist or belongs to someone else.
verification_not_found
404. No verification with that id belongs to your account. A verification is reachable from theverificationId on the claim that started it.
verification_not_running
409. The verification has finished — its claim was proved, the window closed, or the claim was canceled — so there is nothing left to run. Claim the domain again. That opens a new claim with a new token and a verification of its own.claim_not_proved
404. No proved claim with that id belongs to your account. A proof link shares a proof, so there is nothing to publish until one is granted — and a pending, expired or canceled claim never had one.proof_link_not_found
404. No link with that slug was ever published on that claim. Revoking one twice returns this too: what is already taken back is no longer there to take back. This is the holder’s error, raised while managing links on a claim they own. A stranger reading a slug that resolves to nothing getsproof_not_found instead.
proof_not_found
404. No proof resolves at that slug.GET /api/proofs/:slug reveals nothing else: a slug that
was never issued and one that belongs to an account you cannot see read the same.
proof_revoked
410. The holder took the link back. It retracts nothing about the proof itself: it was true on the day it was granted and still is. Ask whoever holds it to publish another link.rate_limited
429. Too many requests. Carries aRetry-After header in seconds.
Enforced per IP on the public surfaces — reading a zone, and the proof page and its API read, which
share one budget — and per verification on POST /api/verifications/:id/runs.
Safe to retry after
Retry-After. Forcing checks in a loop does not make DNS answer faster.