Free · live registry data · no login
Domain Ownership Verification Helper
Generate and check the TXT record a service asks you to add.
How it works
Domain ownership verification helper: build and check the TXT record
Google, Microsoft 365, Meta, Stripe, GitHub and most SaaS tools prove you control a domain by asking you to publish a TXT record. This helper shows the exact hostname and value format for each service, then queries live DNS over HTTPS (Cloudflare and Google resolvers) to confirm the record is visible to the world. Paste the token the service gave you and we tell you whether it has propagated, whether old tokens are cluttering the record, and what to fix if verification keeps failing.
Results appear here after you click Check TXT record.
How this works
- 1
Build the record
We pick the hostname and value format the chosen service expects and show it as a ready-to-paste TXT record.
- 2
Query public DNS
A live TXT lookup over DNS-over-HTTPS returns exactly what Cloudflare's and Google's resolvers see for that hostname.
- 3
Compare and diagnose
We match your token exactly, detect near misses, records on the wrong hostname and stale tokens, and explain the fix.
Frequently asked questions
- How do I verify domain ownership with a TXT record?
- The service gives you a token; you add a TXT record at your DNS host (the company your nameservers point to) with the hostname they specify, usually the root, and that token as the value. Once public resolvers return it, click Verify in the service. This tool confirms the public part.
- Why does Google say the TXT record was not found?
- The usual causes are adding it at the registrar when DNS is hosted elsewhere, pasting it on a subdomain instead of the root, extra quotes or spaces, or simply not waiting for propagation. Check the record here; if we see it on the right hostname, retry verification after a few minutes.
- Can I have multiple TXT records on the same domain?
- Yes. SPF, DMARC (on _dmarc), and any number of verification tokens can coexist on one name; each is a separate record. The only rule is one SPF record per name, so never paste a verification token into your SPF string.
- Should I delete the verification record afterwards?
- Keep it. Google Search Console, Microsoft 365 and Meta re-verify periodically and will drop your ownership (and, for Microsoft, risk mail flow) if the record disappears. Old tokens from services you no longer use can be removed.
- What is the difference between TXT and CNAME verification?
- Both prove control of DNS. TXT puts a token on an existing name; CNAME creates a new hostname pointing at the provider. TXT is preferred because it never conflicts with other records, whereas a CNAME cannot share a name with anything else.
Every MailShrine domain includes WHOIS privacy, transfer lock, Anycast DNS with DNSSEC and two business mailboxes.