Free tools
Domain verification diagnoser
Compare your domain with its expected target and get a DNS diagnosis with fix instructions.
How it works
- Paste the expected record. Enter the full domain, record type and target or verification value supplied by your service.
- Compare the DNS evidence. The engine checks authoritative and public answers, relevant host-entry mistakes, proxy addresses and apex restrictions.
- Open the fix instructions. Read the detected reason and follow the linked provider guide. Retry after editing DNS; incomplete checks are not a failure verdict.
Use the free API
No API key required. Omit the Accept header for JSON. These read-only checks share a per-address rate limit; a 429 response means wait before trying again.
curl --get 'https://app.dodomain.io/api/tools/verify-diagnoser' --data-urlencode 'name=www.example.com' --data-urlencode 'target=customers.example.net' --data-urlencode 'type=CNAME' -H 'Accept: text/markdown'Verification inside your product
DoDomain's connect flow guides customers through setup and verifies their records against authoritative DNS. The DNS provider guides explain where to edit each provider's host and target fields.
Frequently asked questions
Which verification failures can this diagnose?
The checks can identify a wrong host, wrong target, missing record, TXT trailing-dot mismatch, a zone appended to a CNAME target, proxy addresses, resolver disagreement and an apex CNAME restriction. If DNS did not answer, the result is indeterminate.
Is a trailing dot always wrong?
No. A final dot on a hostname marks an absolute name and is normalized for hostname targets. Some DNS panels append the zone to a target entered as relative; follow the provider's convention. In a TXT verification value a dot is literal text, so an extra dot can make the expected value differ.
Why can a working website fail DNS verification?
A Cloudflare proxy can return edge addresses instead of the CNAME target the verifier expects. The tool can identify proxy addresses, but cannot see which origin the proxy forwards to. Follow the provider guide to make the expected DNS record visible.
Does propagation mean I should edit the record again?
Not necessarily. When the authoritative record matches but public resolvers disagree, cached answers may still be expiring. Check the resolver views and the provider instructions before making another change.
Start on the free plan
No card, no sales call: create an app, mint a session, and watch the first domain verify.
More free tools
- DNS provider detector
Which DNS host serves a domain, and whether one-click setup is available there.
- DNS propagation checker
One record, read from the authoritative nameservers and three public resolvers.
- SPF record checker
Parse a domain's SPF, walk its includes, count the lookups against the limit of ten.
- CNAME chain checker
Follow aliases and flag loops, apex CNAMEs and possible flattening.
- DNS record diff
Compare a live DNS snapshot with the expected records you paste in.