SPF
- A single v=spf1 record, not two
- DNS lookups counted through every nested include, limit of 10
- Final rule: -all, ~all, ?all, +all or missing
- ptr mechanism, discouraged
- Your email provider actually included
Free tool
Can someone send an email in your name? Enter your domain. The tool reads your SPF, your DMARC and your DKIM keys, then gives you the exact record to fix.
A DMARC and SPF checker reads the public DNS records that protect a domain’s email. It confirms there is only one SPF record, counts its DNS lookups (10 at most), reads the DMARC policy (none, quarantine, reject) and the report address, then looks for DKIM keys. Every error comes with the corrected record.
The domain is all it takes. Only public DNS is read, nothing is sent to your servers.
What the tool checks
Free, no account needed.
Your result
The short answer
They are three DNS records that protect a domain’s email against spoofing. SPF lists the servers allowed to send in your name: Microsoft 365, Google Workspace, your newsletter tool. DKIM adds a signature to every message, and the receiving server checks that signature against a key published in your DNS. DMARC ties both to the address the reader sees in the From field, then gives the instruction: let it through while monitoring (p=none), send it to spam (p=quarantine) or refuse it (p=reject). It also sends you reports on who is sending with your domain. Without these three settings, a fraudster can email your customers a fake invoice that looks like it came from your address. People search for it as a DMARC checker, an SPF checker or an email authentication test; this page does all three in one pass.
The checks
Four groups, each with its own score. Everything comes from public DNS, read at the time of the test: nothing is guessed.
No email sent, no connection to your mail servers, no mailbox probed. It reads what your DNS publishes for everyone, just like every server that receives one of your messages.
A DKIM key hides under a name chosen by the provider. If the tool does not find it at the six common selectors, it says so plainly: the key may exist under another name.
How it works
A few dozen DNS queries, in a few seconds. It is the same path a receiving server follows when one of your emails arrives.
The grade
Each check is worth one point if it passes, half a point to watch, zero if it is a problem. DMARC weighs 40% of the grade, SPF 35% and DKIM 15%. MX and BIMI inform without counting. A group with nothing to measure, such as DKIM on a domain that sends nothing, drops out of the calculation.
| Grade | Score out of 100 | What it means |
|---|---|---|
| A+ | 95 to 100, no problems | SPF, DMARC and DKIM in place. A fake email in your name gets refused. |
| A | 85 to 94 | Very good. Often DMARC still at quarantine, or a 1024-bit key. |
| B | 70 to 84 | The basics are there. DMARC monitors without blocking, or DKIM is missing. |
| C | 55 to 69 | A broken or too long SPF. Your real mail may fail too. |
| D | 40 to 54 | No DMARC. Nothing tells servers what to do with a fake. |
| F | under 40 | No valid SPF and no DMARC. Anyone can write in your name. |
Three caps apply: a missing or invalid SPF stays at C or lower; a domain without DMARC stays at D or lower; without either, it is an F.
The fixes
In this order. Everything happens at your DNS provider, without touching the mailboxes. The trap is jumping to reject too fast: your own forgotten senders would get refused.
Host: @ Type: TXT
v=spf1 include:spf.protection.outlook.com -all
Host: selector1._domainkey Type: CNAME
selector1-yourdomain-com._domainkey.<tenant>.onmicrosoft.com
Host: selector2._domainkey Type: CNAME
selector2-yourdomain-com._domainkey.<tenant>.onmicrosoft.com
Host: _dmarc Type: TXT
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com Host: @ Type: TXT
v=spf1 include:_spf.google.com ~all
Host: google._domainkey Type: TXT
v=DKIM1; k=rsa; p=<key copied from the Admin console>
Host: _dmarc Type: TXT
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com Replace yourdomain.com with yours, and dmarc@ with a mailbox that exists. For Microsoft 365, <tenant> is the part before .onmicrosoft.com; since May 2025, new domains get a value ending in .dkim.mail.microsoft instead. Always copy the exact value shown in the Defender portal. The checker gives you these lines already filled in with your real domain.
Compare
They do not replace each other. SPF and DKIM each prove one thing; DMARC checks that this proof matches the address your customer sees.
| Criterion | SPF | DKIM | DMARC |
|---|---|---|---|
| What it proves | The sending server is allowed to send for the domain | The message comes from the domain that signed it, unchanged in transit | The domain in the From field matches what SPF or DKIM validated |
| Where it is published | TXT on the domain | TXT or CNAME on selector._domainkey | TXT on _dmarc |
| What is checked | The return address, invisible to the reader | A signature in the message header | The address the reader sees |
| When forwarded | Often fails | Holds, as long as the message is not changed | Passes if SPF or DKIM passes, aligned |
| Without it | Any server can claim to be allowed | DMARC relies on SPF alone, which is fragile | No instructions, no reports |
| What the tool reads | Uniqueness, DNS lookups, all rule, ptr | Six common selectors, key length | Policy, pct, sp, rua, alignment |
Microsoft 365, Google Workspace
Most Quebec small businesses get their email through one of the two. The checker recognizes it from your MX records and puts the right fix first.
SPF with include:spf.protection.outlook.com. For DKIM, Microsoft signs by default with your onmicrosoft.com domain, which does not align with your real domain: you need to create the keys in the Defender portal (security.microsoft.com/authentication, DKIM tab), publish the two CNAME records selector1 and selector2, then turn signing on. DMARC is published at your DNS provider, not in Microsoft 365.
SPF with include:_spf.google.com. The DKIM key is generated in the Admin console: Apps, Google Workspace, Gmail, Authenticate email. Pick 2048 bits, keep the google prefix, publish the TXT record, then click Start authentication.
We can also handle it for you: it is the core of our email protection service for small businesses.
Since February 2024, Google requires senders who send roughly 5,000 or more messages a day to Gmail accounts to have SPF, DKIM, a published DMARC record (p=none at minimum), a From domain aligned with SPF or DKIM, and one-click unsubscribe for promotional mail. Yahoo announced similar rules at the same time. A small business that sends little does not reach that threshold, but Gmail already asks every sender for SPF or DKIM. Thresholds can change: Google’s email sender guidelines are the reference.
Good habits
A reject DMARC policy has to be maintained. These habits keep you from breaking it at the next change.
Go further
A well protected domain does not stop an employee from clicking a booby-trapped link. For the rest, or to have your records set up, here is where to look.
SPF, DKIM and DMARC set up for you, raised all the way to reject, plus phishing filtering.
The three protections explained for a Quebec small business, with examples.
SSL certificate, headers, cookies, visible versions: your site’s grade.
SEO, GEO, security and speed: a report reviewed by a specialist.
Speed test, GEO, Law 25, security: each one in a few seconds.
Setup, security, migration and support for your Microsoft 365 environment.
Does your site show up on Google or in ChatGPT? Our guides explain what SEO is, what GEO is and what AEO is, without the jargon.
Questions and answers
The checker shows what is missing. A specialist lists your sending services, publishes the records, reads the DMARC reports and raises the policy to reject without blocking your real mail. Tell us where you stand and we send you a quote.
Reviewed by Antonio Pazzi, president of OKTO Solutions · updated
We use cookies that are strictly necessary for the site to work. Only with your consent do we add measurement cookies that tell us which pages get read. Refusing costs you nothing, and you can change your mind at any time from the bottom of any page. Cookie details.
Can Google, ChatGPT, AI tools find your website?
We go through your site in depth. You get a clear report with the fixes to make first.
Report sent by email, reviewed by a specialist before it goes out. Privacy policy
Where are you exposed?
A specialist reviews your access, your backups, your email, over a video call.
Book a time