Guide · Domain Intelligence: DNS, RDAP and SSL

Check SPF, DKIM and DMARC for many domains at once

By Tan Solutions · Published · Updated

Short answer

Every domain that sends email should publish three things in DNS: an SPF record (which servers may send for it), DKIM keys (so receivers can verify a signature) and a DMARC record (what to do when both fail, and where to send reports). Checking one domain is three DNS lookups. Checking 300 client or brand domains is the same lookups in a loop, plus knowing which results are real problems.

1. What each record does

SPF is one TXT record on the domain itself, starting with v=spf1. It lists the servers allowed to send mail for the domain, by IP address (ip4, ip6) or by pointing at other records (include, a, mx, redirect), and ends with an all term for everything else. The rules are in RFC 7208 (April 2014, still current, read 15 November 2026).

DKIM puts a public key in DNS. The sending server signs each message, and the receiver fetches the key to check the signature. Keys live under a selector, a name the sender picks, at <selector>._domainkey.<domain>. RFC 6376 explains that selectors exist “to support multiple concurrent public keys per signing domain” (September 2011, Internet Standard, read 15 November 2026). The key-size rule comes from RFC 8301 (January 2018): “Signers MUST use RSA keys of at least 1024 bits for all keys. Signers SHOULD use RSA keys of at least 2048 bits.”

DMARC is one TXT record at _dmarc.<domain>. It ties SPF and DKIM to the address people see in the From line (“alignment”) and states a policy. Since May 2026 the standard is RFC 9989, a Standards Track document that “obsoletes RFCs 7489 and 9091” (read 15 November 2026). Many older guides still cite RFC 7489. The tags that matter most:

Tag Meaning in RFC 9989
p Policy for mail that fails: none, quarantine or reject. A record without p is treated as p=none.
sp, np Policy for subdomains, and for subdomains that do not exist.
rua, ruf Where aggregate reports and failure reports go.
adkim, aspf Strict (s) or relaxed (r, the default) alignment.
t New in RFC 9989: policy test mode.
pct, rf, ri Now listed as “historic” in the DMARC tags registry.

2. What the big mailbox providers require

These are the rules senders hit in practice. All three pages were read on 15 November 2026.

Provider All senders Bulk senders
Gmail SPF or DKIM Over 5,000 messages a day to Gmail accounts: SPF and DKIM, plus DMARC (“can be set to none”), with the From domain aligned to SPF or DKIM
Yahoo SPF or DKIM Both SPF and DKIM, and “a valid DMARC policy with at least p=none - DMARC must pass”; relaxed alignment is acceptable
Outlook.com not stated in the post Over 5,000 emails a day to Outlook.com, Hotmail and Live addresses: SPF must pass, DKIM must pass, DMARC “at least p=none” aligned with SPF or DKIM

Gmail also states that “Sending to personal Gmail accounts requires a DKIM key of 1024 bits or longer” and recommends 2048 bits. Microsoft’s post (2 April 2025, updated 29 April 2025) says non-compliant mail is rejected from 5 May 2025 with “550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.”

A p=none policy therefore meets the minimum at all three. It does not stop anyone from spoofing the domain; that takes quarantine or reject.

3. Checking by hand

For a few domains, dig (macOS, Linux) or nslookup (Windows) is enough:

dig +short TXT example.com
dig +short TXT _dmarc.example.com
dig +short TXT google._domainkey.example.com
nslookup -type=TXT _dmarc.example.com

Look for exactly one record starting v=spf1 in the first answer, exactly one starting v=DMARC1 in the second, and a p= key in the third. The catch is DKIM: you can only find a key if you guess its selector, because DNS does not list them. The sender’s mail platform tells you which selector it uses; the DKIM-Signature header of a real message from the domain shows it as s=.

For 50 or 500 domains, a shell loop works until you need to parse the results, count lookups and compare runs. That is the point to use a script or a tool.

4. Common failures and what they mean

  • Two SPF records. RFC 7208 section 4.5: if more than one v=spf1 record is found, the result is “permerror”. This often happens when a second email service is added as a new record instead of an include in the old one.
  • Too many DNS lookups. RFC 7208 section 4.6.4 limits the terms that cause DNS queries (include, a, mx, ptr, exists and redirect) to 10 “during SPF evaluation”; beyond that the result is “permerror”. The limit counts the lookups inside each included record too, so a record with six include terms can still go over it.
  • +all. It authorises every server on the internet to send as you.
  • The ptr mechanism. RFC 7208 section 5.5 tells publishers not to use it.
  • DMARC stuck on p=none. That is monitoring only. It passes the provider minimum, but spoofed mail is still delivered.
  • Two DMARC records, or no p tag. Keep exactly one record and state the policy explicitly.
  • Old tags. pct= still appears in many records; under RFC 9989 it is historic.
  • DKIM key too short, revoked or in testing. Under 1024 bits fails RFC 8301 and Gmail. An empty p= means the key was revoked. t=y marks a key in testing.
  • DKIM “not found” when DKIM works. Usually the selector was simply not tried.

5. Doing it for a list with our tool

Domain Intelligence reads each domain’s DNS over HTTPS, parses SPF, DMARC and DKIM, and adds registration data and a one-time homepage check. For an email-only audit, turn the website check off. A real input:

{
  "domains": ["example.com", "apify.com", "your-brand.co.uk"],
  "maxDomains": 100,
  "checkDns": true,
  "checkRdap": true,
  "checkWebsite": false,
  "followRegistrarRdap": false,
  "dkimSelectors": ["google", "selector1", "selector2", "s1"],
  "timeoutSecs": 20,
  "maxConcurrency": 4
}

Leave dkimSelectors empty to try 8 common names (default, google, selector1, selector2, k1, s1, mail, dkim). A list you give replaces those 8, so add back any you still want; the limit is 10.

The output is one row per domain. This is a real overview row from a run on 13 November 2026, shortened:

{
  "domain": "apify.com",
  "registrar": "Amazon Registrar, Inc.",
  "expiresAt": "2035-06-02T17:14:10Z",
  "mailProvider": "Google Workspace",
  "dmarcPolicy": "reject",
  "tlsIssuer": "Amazon",
  "tlsDaysToExpiry": 64,
  "checkedAt": "2026-11-13T13:25:57.222Z"
}

The “Email security” view adds a mail object with the details. These are its fields (names only; the values depend on the domain):

Field What it tells you
spf (top level) true if an SPF record was found. It does not mean the record is valid.
mail.spf.valid, mail.spf.errors Whether the record parsed cleanly, and why not: more than one SPF record, more than 10 DNS-querying terms, unknown terms, ptr, +all.
mail.spf.includes, redirect, all, ip4, ip6, dnsLookups What the record delegates to, its all term, how many IP entries it lists and its DNS lookups (since build 0.1.6, the total with includes followed).
mail.dmarc.policy, subdomainPolicy, adkim, aspf, pct The parsed tags; since build 0.1.6 also np, psd and t, with pct marked historic.
mail.dmarc.ruaDomains, rufDomains The domains that receive reports. Email addresses in mail.dmarc.record are hidden.
mail.dmarc.valid, errors Flags a missing or invalid p, a bad pct or more than one DMARC record.
mail.dkim.selectorsChecked, found[] Which selectors were tried, and for each key found: selector, keyType, keyBits, revoked, testing.

Earlier builds differed from the RFCs in a few places; build 0.1.6 (15 November 2026) fixes them. SPF now reports the total DNS lookups with includes followed, and checks the RFC 7208 limit of two void lookups (queries that return no answer). DMARC follows the RFC 9989 tree walk: a subdomain with no record of its own inherits the policy of the domain above it, so mail.google.com shows google.com’s reject. The np, psd and t tags are read, and pct is reported as historic, as RFC 9989 has it. The example rows above come from the run of 13 November, before that build. One thing to know when reading a row: mail.dmarc.valid is false when p is missing, which is stricter than RFC 9989 (receivers treat it as none); read it as “fix this”, not “mail will fail”.

Pricing: from USD 1.25 per 1,000 domains, plus Apify’s own charge for starting a run. Domains with no DNS and no registration, entries that are not domain names, duplicates and domains over your cap are free. It is USD 2.00 per 1,000 domains on the Apify free plan. One domain takes a few seconds; the tool documentation gives about 6 minutes for 100 .com domains with all checks on. Run it on the Apify Store, or schedule it weekly so a changed record shows up before it costs you mail.

6. RDAP vs WHOIS, in one box

7. Limits to know

  • DKIM needs selectors. No tool can list them from DNS; a key under a selector you did not try is reported as not found.
  • Records, not delivery. It reads what is published. Whether a given message passes depends on the server that sent it.
  • Registration lookups are paced to one per second per registry; 1,000 .com domains take about 30 minutes.
  • Public data only. No logins and no proxies; the homepage check, when on, identifies itself as TanForgeBot.

Sources

All read on 15 November 2026. Undated official pages are the current versions on that day.

  1. IETF, RFC 9989: DMARC, May 2026.
  2. IETF, RFC 7208: Sender Policy Framework (SPF), April 2014.
  3. IETF, RFC 6376: DKIM Signatures, September 2011.
  4. IETF, RFC 8301: DKIM algorithm and key usage update, January 2018.
  5. Google, Email sender guidelines, no page date.
  6. Yahoo, Sender Requirements and Recommendations, no page date.
  7. Microsoft, Outlook’s New Requirements for High-Volume Senders, 2 April 2025, updated 29 April 2025.
  8. ICANN, Registration Data Access Protocol (RDAP), no page date.
  9. Tan Solutions, Domain Intelligence, run of 13 November 2026, verified 14 November 2026; build 0.1.6 of 15 November 2026.

Next steps

Related guides