Bulk TXT record lookup: the TXT records of every domain on a list
In short: Paste domains or hostnames and read every TXT record each one publishes, with SPF, DMARC and common site-verification records named and a flag for domains with more than one SPF record. Limit: Labels come from the start of each record's text. They don't check that a record is valid or correct.
A bulk TXT record lookup reads the TXT records of many domains in one run. Paste up to 100 domains or hostnames, or 500 after a free Google sign-in, and each row lists every TXT record with SPF, DMARC and verification records named, and a flag where a domain publishes more than one SPF record. DNS only. Download the results as CSV.
Price: this tool is free. Checking a whole email list is from $9/mo, and the first 100 checks are free with Google, no card. Check your list free nowSee pricing
Sample result
globex.example publishes two SPF records; acme.example publishes one, plus a Google site-verification token.
- Domain
- globex.example
- TXT records
- 2
- Recognised
- SPF
What this means for you
Two SPF records fail SPF with a permanent error, so merge them into one.
- Every TXT record in full
- SPF, DMARC and verification named
- More than one SPF flagged
- Underscore names work; CSV out
- TXT
- SPF
- DNS
By SimpleVerifier Team · Last updated
Checking the DNS of a whole lead list?
- Paste the list here as domains, hostnames or email addresses: up to 100 a run, or 500 after a free Google sign-in. Filter the rows and download the CSV.
- Upload or paste it at /verify. Every address gets a live mailbox check, and the first 100 email checks are free with a Google sign-in, no card.
How do I look up the TXT records of many domains at once?
- Paste domains, hostnames or email addresses, one per line, up to 100 a run or 500 after a free Google sign-in. Underscore names such as _dmarc.acme.com work too.
- Press Look up TXT records. Each name gets one TXT query to public DNS, 25 names a request; nothing is sent to the domains' own servers.
- Read each row: the full text of every TXT record, the kinds we recognise (SPF, DMARC, Google or Microsoft site verification and others), and a flag for more than one SPF record.
- Filter to the rows that need work, such as multiple SPF records or no TXT at all, and download the CSV.
Example
- You enter
- Two names:
acme.example(an SPF record and a Google site-verification record) andglobex.example(two SPF records). - You get
- acme.example: Has TXT records, recognised as SPF and Google site verification, each record in full. globex.example: flagged 2 SPF records, which fail SPF until merged. Download the CSV.
- Limits
- Up to 100 a run without an account and 500 when signed in with Google, counted over a minute. 25 names a request; DNS only.
What does a bulk TXT lookup show?
A TXT record is free-form text attached to a DNS name. RFC 1035 defines it as one or more character strings, and today it carries SPF policies, DMARC and DKIM keys, and the tokens that prove you control a domain to a service. The lookup returns every TXT record on each name you paste, with the strings of a long record joined back together.
Rows are labelled where the record text starts with a tag we know: v=spf1 (SPF), v=DMARC1, v=DKIM1, and verification prefixes such as google-site-verification= and MS=. The label comes from the text alone. It says what kind of record it is, not whether it is correct for your setup.
Why does it flag more than one SPF record?
A domain must publish a single SPF record. RFC 7208, section 4.5 says that when a name has more than one record starting v=spf1, the result is a permanent error, so receivers can treat SPF as failed for every message. It usually happens when a second service's instructions are followed by adding a new record instead of merging it into the old one.
The flag counts records that begin v=spf1 on the exact name you pasted. To merge two records into one, use the SPF record merger.
Can I look up _dmarc or other underscore names?
Yes. Paste the full name, such as _dmarc.acme.com, default._bimi.acme.com or selector1._domainkey.acme.com, and the tool queries it as written. A bare domain is looked up as that domain only; it doesn't add the underscore names for you. For the DMARC policy of a list graded and explained, the bulk DMARC checker does the parsing.
How is this different from the bulk DNS lookup?
| This tool | Bulk DNS lookup | |
|---|---|---|
| Record types | TXT only | A, AAAA, CNAME, NS, MX and TXT, as you choose |
| Record text | Every record in full, kinds named | Records listed as returned |
| Repeat SPF flag | Yes | No |
Who uses this tool, and for what?
- Email deliverability teams
- Find domains on a list that publish two SPF records, which fail SPF until they are merged.
- IT administrators
- See which verification tokens a set of domains still publish, before cleaning up old services.
- Security reviewers
- Read the TXT records of a vendor or subsidiary list in one pass.
- Sales researchers
- Spot which companies on a list verified a given service, such as Google Workspace, from their DNS.
What can’t this tool tell you?
- Labels come from the start of each record's text. They don't check that a record is valid or correct.
- Only the exact name you paste is queried; underscore names are not added for you.
- Public DNS can return an answer cached for up to the record's TTL, so a record changed minutes ago may not show yet.
- Up to 100 names a run without an account, 500 signed in.
Common questions
- How do I look up TXT records for many domains?
- Paste the domains into a bulk TXT record lookup like this one. It queries each name's TXT records over DNS and shows every record, with a CSV of the results.
- Is this bulk TXT lookup free?
- Yes. It is a free tool: up to 100 names a run with no account, and up to 500 a run when you sign in with Google, with no card.
- Does it connect to the domains' servers?
- No. It asks public DNS for the records. Nothing is sent to the websites or mail servers of the domains you paste.
- Why does a domain show no TXT records?
- Either the name has none, or the query didn't complete. A name that doesn't exist in DNS is shown separately as Doesn't exist, and a timeout as Lookup failed, so you can run those again.
- Does it find DKIM keys?
- Only if you paste the full DKIM name, such as selector1._domainkey.acme.com. A DKIM key lives at a selector chosen by the sender, so it can't be found from the bare domain alone; the bulk DKIM checker tries common selectors.
- What is the difference from a bulk DNS lookup?
- The bulk DNS lookup returns several record types at once. This tool returns only TXT records, shows their full text, and labels SPF, DMARC and verification records.
Sources
A tidy list can still be full of dead addresses.
Extracting, deduplicating and syntax checks all work on the text of an address. None of them can tell whether the mailbox exists. Only the server that hosts it can answer that, through an SMTP check, and that is what the paid product does.
- Upload the cleaned file as it is: CSVs up to 100,000 rows
- A real SMTP mailbox check on every row, with catch-all detection
- Small list? Starter at $9/mo covers 2,500 emails a month, cancel anytime
Plans from $9 a month, 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.