The guest list
SPF says which servers are allowed to send email for your domain. Anything not on the list should be treated with suspicion. One record only — and it can name at most 10 DNS lookups.
DMARC Checker — is your email setup getting you rejected?
Enter your domain and we’ll check its real, public DNS records right now — SPF, DMARC, DKIM and mail servers — then tell you in plain English what’s missing and exactly how to fix it.
Check your domain
Paste a domain, a full website address, or an email address — we’ll sort out the domain for you.
Try an example:
·
Privacy: this check reads only public DNS records — the same records anyone on the internet can see. Your domain isn’t stored, tracked, or added to any list.
Checking your domain…
- SPF record
- DMARC policy
- DKIM selectors
- Mail servers (MX)
Results for —
Your exact fixes
Written from this domain’s actual records — in the order we’d do them.
About DKIM: DKIM keys can’t be listed from outside a domain — there’s no public directory of selectors. We probe the common selectors used by Google, Microsoft, Mailchimp and other major senders. “Not found” means not found on those selectors, not proof that no DKIM exists anywhere.
About inbox placement: passing these public DNS checks is the entry requirement for Google and Microsoft — it does not by itself guarantee the inbox. Content, list quality, engagement and sending reputation still matter.
Want us to fix your email setup for you?
Send us this result and we’ll pick it up from there — we’ll review your SPF, DMARC and DKIM, tell you what needs changing, and help you move to full enforcement safely.
Opens your own email app with everything pre-filled, addressed to Learn With Maneeza. Nothing is sent until you press send in your app.
Looks like no email app opened.
No problem — use one of these instead. Your result is already written out for you.
The three records, in one line each
You don’t need to be technical to fix this. You just need to know what each record is for.
The signature
DKIM adds a cryptographic signature to every email you send, so the receiving server can prove the message really came from you and wasn’t altered on the way.
The bouncer’s instructions
DMARC tells receivers what to do when SPF or DKIM don’t line up with your domain — watch it, quarantine it, or reject it — and where to send you reports about it.
What Google & Yahoo require (since Feb 2024)
- SPF and DKIM set up for your sending domain
- A DMARC record published —
p=noneis the minimum to comply - Applies in full to bulk senders (5,000+ messages a day to Gmail), but the same setup is expected best practice for everyone
- One-click unsubscribe and spam rates kept below 0.3%
What Microsoft requires (since May 2025)
- SPF, DKIM and DMARC all required for high-volume senders to Outlook.com / Hotmail
- Messages that fail authentication can be rejected outright, not just filtered
- DMARC at
p=nonewith valid alignment is the stated minimum - The direction is the same everywhere: authenticate, or get rejected
Why p=none is not protection
A DMARC policy of p=none means “watch and report, but deliver anyway.” It satisfies the basic Google and Microsoft requirement — but it stops nobody from sending fake email pretending to be your domain. Real protection only starts at p=quarantine (spam folder) and is complete at p=reject (refused outright). The safe path is: start at p=none with reporting on, confirm every legitimate sender aligns, then step up to quarantine, then reject.
What to fix first
1. No DMARC at all — publish one today; it takes minutes and it’s the record the big inboxes check first. 2. DKIM missing or off — turn it on inside every platform that sends as you (your mailbox, your newsletter tool, your CRM, your shop). 3. SPF over 10 lookups or split across two records — this silently breaks SPF entirely; tidy the sender list. 4. Stuck on p=none — once reports show only your real senders, step the policy up.
Common questions
Is this check accurate? Where does the data come from?
Yes — it queries the same public DNS-over-HTTPS services (Google, with Cloudflare as backup) that mail servers themselves consult. The record text shown on each card is copied verbatim from your domain’s live DNS, not generated or guessed.
The checker says no DKIM was found. Does that mean I have no DKIM?
Not necessarily. DKIM selectors aren’t published in a directory, so no outside tool can list them all. We probe 20 of the most common selectors (Google, Microsoft, Mailchimp, and others). If none match, the honest answer is “couldn’t confirm” — check inside each platform that sends email for you; if DKIM is on, it will show you the exact selector it uses.
My DMARC is p=none. Am I compliant — and am I protected?
Compliant with the minimum, yes: Google and Microsoft both accept p=none as the starting point. Protected, no: p=none tells receivers to deliver failing mail anyway. Move to p=quarantine, then p=reject, once your reports show all your legitimate senders passing.
What does “SPF lookup count” mean, and why 10?
Every include, redirect, mx, a, ptr or exists mechanism in your SPF record costs a DNS lookup when a receiver checks it, and the SPF specification caps the total at 10. Go over and SPF fails permanently for everyone — a very common silent breakage on domains that have added many sending tools over the years.
Will fixing these records guarantee my emails land in the inbox?
No — and be wary of anyone who promises that. Correct SPF, DKIM and DMARC get you past the authentication gate that Google and Microsoft now enforce. After that, placement still depends on what you send, who you send it to, and how recipients engage with it.
Do you store my domain or my results?
No. The check runs entirely in your browser against public DNS. There is no database behind this page and nothing is saved. The only time your result goes anywhere is if you tap the email button — and then it travels through your own email app, written by you.