Enter your sending domain
Use the domain in your From address, not necessarily your main company domain if they differ.
SPF, DKIM and DMARC checker
Try Our Free SPF, DKIM and DMARC checker
Enter your sending domain to see whether SPF, DMARC and a common DKIM selector are published, and what to fix if they aren't.
How the checker works
- Step 01
- Step 02
We look up the records
SPF and DMARC live at fixed, known locations, so those two are read directly. DKIM is checked against a list of common provider selectors.
- Step 03
Read what's missing
Each record is shown as found, missing, or misconfigured, with what a fix actually looks like.
- Step 04
Fix it with your DNS provider
SPF, DKIM and DMARC are all published as TXT records. Add or correct them where your domain's DNS is managed, then re-check.
How the checker works
SPF and DMARC are published at fixed, predictable locations: SPF as a TXT record on the domain itself, DMARC as a TXT record at _dmarc.yourdomain.com. Both are looked up directly, so a miss here is a real miss, not a limitation of the check.
DKIM works differently. It's published at a selector-specific address that only your mail provider knows, like google._domainkey.yourdomain.com or selector1._domainkey.yourdomain.com. There's no way to discover the correct selector from outside, so this tool tries a list of common provider selectors and reports what it finds. A 'not found' result for DKIM means none of those common selectors matched, not that DKIM is confirmed missing: check your mail provider's setup instructions for your exact selector if you're unsure.
How this compares to paid tools
Full deliverability suites monitor these records continuously and test far more than three DNS lookups. This gives you the same three answers in seconds, for free, whenever you want a quick check.
| Feature |  | Deliverability suite | Manual DNS lookup |
|---|---|---|---|
| Price | Free | $99 to $300 per month | Free, but slower |
| SPF and DMARC checked directly | |||
| DKIM checked against common selectors | Manual only | ||
| Plain-language explanation per record | Varies | ||
| Free with no card | |||
| Continuous monitoring and alerts | |||
| Inbox placement testing |
Who this is for
Founders setting up a new sending domain
SPF, DKIM and DMARC all need to be right before the first real send. Check them once during setup, not after deliverability drops.
Anyone whose emails started landing in spam
A record that was fine at setup can break silently: a DNS migration, a new email tool added without updating SPF, a typo in a record. Check first before assuming it's a copy problem.
Agencies onboarding a new client domain
Confirm the client's domain is actually authenticated before running any campaign on it. A missing DMARC record is a five-minute fix that's easy to miss.
Ops leads doing a deliverability audit
Run every sending domain through once as a baseline, then re-check after any DNS change.
Popular use cases
01 · Use case
Pre-launch check on a new domain
Confirm all three records are in place before the domain sends its first real campaign.
02 · Use case
Diagnosing a sudden spam-folder problem
Rule domain authentication in or out before assuming the issue is your copy or your list.
03 · Use case
Verifying a DNS change actually took effect
DNS changes can take time to propagate. Re-run the check after making a change to confirm it's live.
Frequently asked questions
Something not covered? Talk to our team.
No. The spam checker reads your email copy for risky language and formatting. This tool reads your domain's DNS records. Both affect deliverability, but they're independent checks: clean copy on an unauthenticated domain still lands in spam, and a fully authenticated domain still gets filtered if the copy reads as promotional.
