TXT / SPF Lookup
Read TXT records including SPF verification policies.
Read the guideRun the tool
JVR Software’s server processes the public target you enter. The diagnostic is rate-limited. Use a system you own or are authorised to check.
More information
Back to the toolWhat it is and when to use it
TXT / SPF Lookup reads the text records published at a precise DNS name. Hosting providers use TXT for ownership verification, and mail systems use it for policies such as SPF and DMARC. It is useful when setup instructions say to publish a token but the receiving service reports that it cannot see it.
How it works
The tool asks for TXT at the name you enter. Several records may exist there. SPF records start with v=spf1, and unrelated verification records can coexist at the same name. A provider can split one long TXT record into several quoted strings. Multiple strings in a single record differ from multiple separate policies.
How to use it
- Copy the exact record name from the provider's setup instructions.
- Run TXT Lookup and find the record with the expected prefix or value.
- If checking mail authentication at a special label, use Email DNS Health for the built-in DMARC and optional DKIM selector checks.
Worked example
If a provider asks you to publish an apex ownership token, query the bare domain. Compare every character against the provider's instructions. If a token is missing, confirm that the DNS panel did not append the domain twice when you saved the name.
Reading the result
Identify TXT records by their content, then inspect their TTL. More than one TXT record is normal. More than one SPF policy at the same name can make SPF evaluation fail. Only the first issue is directly visible in a simple record list.
A verification service may ask for a record at a subdomain even when it describes verifying the whole site. Query the precise record owner name printed in the provider’s instructions. When several TXT values appear, compare the expected string to the complete individual record instead of assuming that every TXT answer belongs to the same service.
Common mistakes and limits
Seeing a TXT value proves that this resolver returned it. It does not prove that the provider has accepted verification or that a received message passes authentication. Do not put passwords or private keys in DNS. Verification values intended for DNS should be treated as visible to anyone.
