TXT record lookup
Show every TXT record on a name: SPF, domain verification codes and the rest, straight from its authoritative nameservers.
Part of the DNS lookup.
Comparing all 13 public resolvers takes a few seconds.
What this checks
TXT records hold free text on a DNS name. Most domains carry several: an SPF record (v=spf1 …), verification codes from Google, Microsoft and other services that want proof you own the domain, and sometimes keys or policies for other systems.
The lookup asks the domain's own authoritative nameservers, so a record you just added shows at once, without waiting for caches to expire. Switch to a public resolver in the form to see what the rest of the internet sees, or compare 13 of them with the DNS propagation check.
Some TXT records live on their own name rather than the domain itself. Look these up by their full name:
| Record | Name to look up |
|---|---|
| DMARC | _dmarc.example.com |
| DKIM | selector._domainkey.example.com |
| MTA-STS | _mta-sts.example.com |
| TLS-RPT | _smtp._tls.example.com |
Common problems and fixes
The record doesn't show. Check you added it at the DNS host the domain actually uses (the nameserver check shows which that is), and that the panel didn't add the domain twice (example.com.example.com).
Quotes inside the value. Most DNS panels add the surrounding quotes themselves; quotes you type become part of the record. Enter the value without them unless your provider says otherwise.
A long record looks split. A single TXT string holds at most 255 characters, so long values (DKIM keys, big SPF records) are stored as several strings that are joined when read. That is normal.
Two SPF records. Many services ask you to "add a TXT record" with v=spf1. A domain may only have one, so merge them. The SPF checker tests the record and counts its lookups.
For other record types, use the full DNS lookup.