TXT · _dmarc · default._bimi
TXT record lookup
Read every TXT record of a domain, together with its DMARC and BIMI records, and see at a glance which one is SPF, which is a policy and which is a verification token for some service.
What TXT records hold
TXT records carry free-form text that other systems read: SPF lists who may send mail for the domain, DMARC (at _dmarc) says what receivers should do with mail that fails authentication, BIMI (at default._bimi) points to a brand logo, and services such as Google, Microsoft 365 or Meta ask you to publish a verification token to prove you own the domain.
One DNS string holds at most 255 bytes, so long values such as DKIM keys are published as several strings that receivers join back together. The tool shows the joined value and how it was split, which helps when a DNS panel has cut a value in the wrong place.
This page recognises records and shows their basics. For a full evaluation of SPF lookups, DMARC policies and DKIM keys, use the sister site MailTraceKit, for example its SPF checker or DMARC checker.
Frequently asked questions
Why is my TXT record split into several strings?
A single DNS character string is limited to 255 bytes. Longer values are stored as several strings in one record, and SPF and DKIM readers concatenate them without adding spaces.
Can a domain have more than one TXT record?
Yes, as many as you like, but only one of them may be an SPF record. Two records starting with v=spf1 make SPF fail with a permanent error.
Where are DKIM keys?
At selector._domainkey under the domain, and the selector name is only known from a signed message. Enter the full name here, or use MailTraceKit’s DKIM checker, which also decodes the key.