How do I check the TXT record of a domain?

Enter the domain above and press Look up TXT records. You get the TXT records on the domain plus those at _dmarc, default._bimi, _mta-sts and _smtp._tls. From a terminal, nslookup -type=txt example.com or dig TXT example.com shows the domain's own records only.

What is a TXT record for domain verification?

A record containing a token a service gave you, such as google-site-verification=… or MS=ms12345678. The service looks the record up to confirm you control the domain's DNS. This tool names the common ones, so you can see which services a domain has verified with.

Can I delete a TXT record after verification?

Sometimes. Some services only check once, but others, including Google, re-check periodically and may unverify the domain if the token disappears. Check the service's own instructions first; leaving an unused token in place does no harm to email.

TXT record lookup: see and label every TXT record

A TXT record lookup returns the text records a domain publishes in DNS. Most are either email authentication (SPF, DMARC, DKIM, BIMI) or verification tokens that prove ownership to services like Google or Microsoft 365. This tool also checks the underscore names email records live at, labels every record and flags duplicate SPF or DMARC records.

SimpleAPI

Sample result

acme.example publishes SPF and DMARC records, but no BIMI record.

Host: acme.example
SPF: include:_spf.google.com ~all
DMARC: p=quarantine

What this means for you

These records tell inboxes who may send for you and what to do with fakes.

Next step:Run the full deliverability audit

TXT on the domain and its email names
_dmarc, default._bimi, _mta-sts, _smtp._tls
Add a DKIM selector to read its key
Labels SPF, DMARC and verification tokens

TXT
SPF
DMARC

By SimpleVerifier Team · Last updated October 17, 2026

How do I look up a domain's TXT records?

Enter a domain, or a specific name such as _dmarc.example.com. A pasted URL or email address is trimmed to the host.
Optionally add a DKIM selector (for example s1 or google) to fetch that DKIM key too.
Press Look up TXT records. The domain and its _dmarc, default._bimi, _mta-sts and _smtp._tls names are checked in one go.
Read the labels and any problems flagged at the top, then follow a label's link to check that record in depth.

Example

You enter: The domain acme.example.
You get: The domain publishes an SPF record (v=spf1 include:_spf.google.com ~all) and _dmarc.acme.example publishes v=DMARC1; p=quarantine, each labelled. default._bimi.acme.example has no record.
Limits: One name per lookup and 10 lookups a minute per connection. DKIM is read only for a selector you enter.

What is a TXT record?

A TXT record is a DNS record that holds free-form text, defined in RFC 1035. DNS itself gives the text no meaning; other systems agree on formats for it. SPF starts with v=spf1, DMARC with v=DMARC1, DKIM keys with v=DKIM1 or p=, and services from Google to Stripe ask you to publish a random token to prove you control the domain.

A single TXT string is limited to 255 characters, so long records such as DKIM keys are published as several strings that receivers join back together. This tool shows them already joined, the way a mail server reads them.

What is a TXT record used for in email?

Almost all of email authentication lives in TXT records. SPF on the domain lists the servers allowed to send for it (RFC 7208); DMARC at _dmarc sets the policy for messages that fail (RFC 7489); DKIM public keys sit at selector._domainkey; BIMI at default._bimi points to a logo; and MTA-STS and TLS reporting live at _mta-sts and _smtp._tls.

Because those records sit at different names, a plain TXT lookup of the domain misses most of them. This tool queries each name, so one lookup shows the whole email setup. For the full picture with mail servers and every other record type, use the DNS lookup.

Can I have multiple TXT records for a domain?

Yes, a domain can publish any number of TXT records, and most busy domains have a dozen or more verification tokens. The exceptions are SPF and DMARC. RFC 7208 section 3.2 says a domain must not have more than one SPF record, and receivers return a permanent error when they find two; with two DMARC records, receivers ignore DMARC altogether.

This tool flags both. The fix is to merge the SPF mechanisms into one record with the SPF generator and keep a single DMARC record. Verification tokens can usually be removed once the service has confirmed the domain, but some services re-check them periodically, so check each provider's documentation before deleting.

Is this different from a DNS lookup?

	TXT record lookup	DNS lookup
Names checked	Domain, _dmarc, default._bimi, _mta-sts, _smtp._tls, DKIM selector	The name you enter, plus _dmarc
Record types	TXT only	A, AAAA, CNAME, MX, NS, TXT, SOA, CAA
Labels verification tokens	Yes, by service	Yes, inline
Flags duplicate SPF or DMARC	Yes	Duplicate SPF only

Who uses this tool, and for what?

Email senders: Check SPF, DMARC, BIMI, MTA-STS and a DKIM selector in one lookup after a DNS change, and catch a second SPF record before it breaks authentication.
IT admins: Confirm a verification token for Google Workspace, Microsoft 365 or an SSO provider is live before pressing Verify.
Agencies: Audit a client's domain: which services it's verified with, and whether its email records exist at the right names.
Security teams: Inventory third-party verification tokens to see which services a domain has been connected to.

What can’t this tool tell you?

DKIM keys are only checked for the selector you enter; selectors can't be listed from DNS.
Labels come from known record formats and token prefixes; an unfamiliar token is shown as Other or as a generic verification token.
It checks syntax-level problems (duplicates, misplaced DMARC), not whether an SPF record's includes are within the 10-lookup limit; use the SPF checker for that.
Results reflect a public resolver now; recent changes may still be propagating.

Common questions

What is a TXT record?: A DNS record that holds text. Mail servers read SPF, DMARC, DKIM and BIMI from TXT records, and services such as Google Search Console, Microsoft 365 and Stripe use TXT tokens to confirm you own a domain. Enter a domain above to see its TXT records with each one labelled.
How do I check the TXT record of a domain?: Enter the domain above and press Look up TXT records. You get the TXT records on the domain plus those at _dmarc, default._bimi, _mta-sts and _smtp._tls. From a terminal, nslookup -type=txt example.com or dig TXT example.com shows the domain's own records only.
What is a TXT record for domain verification?: A record containing a token a service gave you, such as google-site-verification=… or MS=ms12345678. The service looks the record up to confirm you control the domain's DNS. This tool names the common ones, so you can see which services a domain has verified with.
Can I delete a TXT record after verification?: Sometimes. Some services only check once, but others, including Google, re-check periodically and may unverify the domain if the token disappears. Check the service's own instructions first; leaving an unused token in place does no harm to email.
Can I have multiple TXT records?: Yes, as many as you need, except for SPF and DMARC. A domain must publish exactly one SPF record and one DMARC record; two of either breaks it. The tool flags duplicates at the top of the result.

Sources

You audited one domain. Cold outreach means thousands.

This tool checks a domain you type in. It will not tell you which addresses at that domain are real.

Bulk mailbox verification with real SMTP checks
The email finder — name plus company to a verified address
Website enrichment for emails, owner names and socials

Get started — $29.99/mo See the published limits first

One plan, cancel anytime, no contract. Sign in with Google and your first 100 email checks are free, no card. The free tools stay free either way.