Frequently Asked Questions
What is a TXT record lookup?
A TXT record lookup queries the DNS for all TXT-type records published under a domain name. It returns the raw record values along with TTL data. This tool performs the lookup in real time using your choice of DNS resolver — Google, Cloudflare, or OpenDNS — and automatically classifies each record as SPF, DMARC, DKIM, or a verification record.
Can a domain have multiple TXT records?
Yes — a domain can have as many TXT records as needed. In practice, most domains have several: one SPF record, one DMARC record, one or more DKIM records (one per selector/sending service), plus domain verification records for Google, Microsoft, or other platforms. Note that a domain should only ever have one SPF record — multiple SPF records cause SPF to fail.
What does it mean if SPF, DKIM, or DMARC shows "Not Found"?
It means the record is not published in DNS for this domain. Missing SPF means receiving servers can’t verify your authorised senders — increasing spam likelihood. Missing DKIM means emails aren’t signed, reducing trust. Missing DMARC means you have no policy controlling what happens when SPF or DKIM fails, and you’re not receiving any abuse reports. All three should be present for good deliverability.
How often do TXT records update?
TXT record changes propagate based on the TTL (Time to Live) value of the record. A TTL of 3600 means resolvers cache the record for up to 1 hour before fetching a fresh copy. Changes typically take between a few minutes and 48 hours to propagate globally, depending on the TTL and downstream resolver cache times. During migrations, temporarily lowering your TTL to 300 seconds speeds up propagation.
What is the difference between a TXT record and other DNS records?
DNS record types serve different purposes: A records map a domain to an IP address, MX records define mail servers, CNAME records create aliases, and NS records define nameservers. TXT records store free-form text and are used for verification and policy publishing — they don’t affect how your domain resolves or routes traffic, but they’re read by mail servers and third-party services.
Why does my SPF record not show up in the lookup?
If SPF is missing from results, the most common causes are: the record hasn’t been added yet, it was added to the wrong subdomain (should be on the root domain
@), DNS changes haven’t propagated yet (wait up to 48 hours), or the record has a syntax error that prevents it being recognised. Try switching to a different DNS resolver in the dropdown — Google and Cloudflare sometimes reflect changes at different speeds.
