Trois-Rivières, serving all of Quebec 450 231-3836 info@oktosolutions.ca

Free tool

Free DMARC and SPF checker

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.

Check your domain’s email

The domain is all it takes. Only public DNS is read, nothing is sent to your servers.

What the tool checks

  • SPF: uniqueness, 10 DNS lookups, all rule
  • DMARC: policy, reports, alignment
  • DKIM at common selectors
  • MX servers, detected provider
  • BIMI, optional

Free, no account needed.

The short answer

What are SPF, DKIM and DMARC?

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

What does the checker look at in your DNS?

Four groups, each with its own score. Everything comes from public DNS, read at the time of the test: nothing is guessed.

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

DMARC

  • Published on _dmarc, only once
  • Policy p=none, quarantine or reject
  • pct below 100%, subdomains (sp)
  • rua report address, external authorization
  • adkim and aspf alignment

DKIM

  • Microsoft 365 selectors selector1, selector2
  • Google Workspace selector google
  • Selectors default, k1, s1
  • TXT or CNAME record
  • Key length: 1024 or 2048 bits

Mail servers, BIMI

  • The domain’s MX servers
  • Recognized provider: Microsoft 365, Google Workspace
  • Domain that receives nothing, null MX
  • BIMI, optional, no effect on the grade

What the tool never does

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.

An honest word about DKIM

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

How does the DMARC and SPF check work?

A few dozen DNS queries, in a few seconds. It is the same path a receiving server follows when one of your emails arrives.

  1. You enter the domain. yourdomain.com, the website address or even an email address: the tool keeps only the domain.
  2. The MX records are read. They tell who receives your mail. The tool recognizes Microsoft 365 or Google Workspace and adapts its fixes.
  3. The SPF record is unfolded. Every include is followed to the end, the way a receiving server does it, to count the real DNS lookups.
  4. DMARC is read. On _dmarc.yourdomain.com, then on the parent domain if you entered a subdomain.
  5. DKIM keys are looked up. At the six most common selectors. The length of every key found is measured.
  6. Each finding gets a status. Passed, watch, problem or not applicable, with the exact DNS record to copy whenever something needs fixing.
Why does it matter? The most profitable fake email for a fraudster is the one that looks like it came from you: a bank account change sent to your customer, an invoice sent to your accountant. A reject DMARC policy gets it refused before it arrives.

The grade

How is the A+ to F grade calculated?

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.

DMARC and SPF checker grading scale
GradeScore out of 100What it means
A+95 to 100, no problemsSPF, DMARC and DKIM in place. A fake email in your name gets refused.
A85 to 94Very good. Often DMARC still at quarantine, or a 1024-bit key.
B70 to 84The basics are there. DMARC monitors without blocking, or DKIM is missing.
C55 to 69A broken or too long SPF. Your real mail may fail too.
D40 to 54No DMARC. Nothing tells servers what to do with a fake.
Funder 40No 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

How do I fix my SPF, DKIM and DMARC records?

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.

  1. List everything that sends in your name. Microsoft 365 or Gmail, of course, but also the newsletter, the invoicing software, the website form, the CRM. A forgotten service means legitimate mail that will end up refused.
  2. Publish a single SPF record. One v=spf1 line that includes every service and ends with ~all or -all. Two SPF lines make an invalid SPF.
  3. Keep SPF under 10 DNS lookups. Remove services that no longer send. A sending subdomain for the newsletter keeps the main line short.
  4. Turn on DKIM at every service. Microsoft 365 in the Defender portal, Google Workspace in the Admin console, the newsletter tool in its domain settings.
  5. Publish DMARC in monitoring mode. v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com, pointing to a mailbox that exists. Nothing is blocked: you only receive the reports.
  6. Read the reports for a few weeks. They show every server that sends with your domain. Fix the legitimate ones that fail.
  7. Move to p=quarantine, then p=reject. Quarantine first: a fake lands in the spam folder. Reject next, once nothing legitimate fails.
  8. Lock down domains that send nothing. An old domain, a variant bought to protect your brand: v=spf1 -all and a DMARC at p=reject. Fraudsters love forgotten domains.
Microsoft 365: the records
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
Google Workspace: the records
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

SPF vs DKIM vs DMARC: what is the difference?

They do not replace each other. SPF and DKIM each prove one thing; DMARC checks that this proof matches the address your customer sees.

CriterionSPFDKIMDMARC
What it provesThe sending server is allowed to send for the domainThe message comes from the domain that signed it, unchanged in transitThe domain in the From field matches what SPF or DKIM validated
Where it is publishedTXT on the domainTXT or CNAME on selector._domainkeyTXT on _dmarc
What is checkedThe return address, invisible to the readerA signature in the message headerThe address the reader sees
When forwardedOften failsHolds, as long as the message is not changedPasses if SPF or DKIM passes, aligned
Without itAny server can claim to be allowedDMARC relies on SPF alone, which is fragileNo instructions, no reports
What the tool readsUniqueness, DNS lookups, all rule, ptrSix common selectors, key lengthPolicy, pct, sp, rua, alignment

Microsoft 365, Google Workspace

What to publish for Microsoft 365 or 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.

Microsoft 365 (Outlook 365)

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.

Google Workspace

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.

What Gmail and Yahoo require from bulk senders

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

8 habits to keep your domain’s email protected

A reject DMARC policy has to be maintained. These habits keep you from breaking it at the next change.

  • Run the check again after every new sending service. A newsletter added without its include means mail in spam folders.
  • One SPF record per domain. The second one does not add to the first: it breaks both.
  • Count lookups before adding an include. The eleventh one breaks the whole SPF, not just the last service.
  • Aim for p=reject. p=none monitors. It protects nobody as long as it stays there.
  • Keep a rua mailbox someone actually reads. Reports nobody opens are useless.
  • Prefer 2048-bit DKIM keys. Rotate the key at your provider when the published one is 1024 bits.
  • Protect dormant domains too. v=spf1 -all with a reject DMARC takes five minutes.
  • Write down who has DNS access. The day a fraudulent email goes around, nobody wants to hunt for the registrar password.

Questions and answers

DMARC, SPF and DKIM questions

How do I check my DMARC record?
Enter your domain in the checker at the top of this page. It reads the TXT record at _dmarc.yourdomain.com and tells you whether it is unique, which policy it applies (none, quarantine, reject), whether it covers 100% of messages and where reports go. From a command line: nslookup -type=txt _dmarc.yourdomain.com, or dig TXT _dmarc.yourdomain.com.
Is this DMARC checker free?
Yes. No account, no email required to see the result. The tool only reads the public DNS of the domain you enter, the same records every receiving server reads when one of your emails arrives. If you want a specialist to review the result, you can ask for a detailed report at no cost.
How do I check my domain’s SPF record?
The checker works as an SPF checker: it reads the v=spf1 line, confirms there is only one, follows every include to count DNS lookups (10 at most under RFC 7208) and checks the final rule. -all or ~all are fine; ?all, +all or a line without all let fakes through.
Why can’t the tool find my DKIM key?
A DKIM key is published under a name the provider picks, the selector. The tool tries the six most common ones: selector1, selector2, google, default, k1, s1. If your service uses another one, the key may still exist. Open an email received from your domain and show the headers: the selector appears after s= in the DKIM-Signature line.
How do I set up DMARC for Microsoft 365 (Outlook 365)?
Microsoft 365 does not publish DMARC for you: it goes in at your DNS provider. Publish an SPF record with include:spf.protection.outlook.com, turn on DKIM in the Defender portal (two CNAME records, selector1 and selector2), then add the _dmarc TXT record at p=none with a rua address. Move to quarantine, then reject, once the reports are clean.
Which SPF and DMARC records for Google Workspace?
SPF: v=spf1 include:_spf.google.com ~all, plus any other service that sends for you. DKIM: generate the key in the Admin console (Apps, Google Workspace, Gmail, Authenticate email), publish the google._domainkey TXT record, then start authentication. DMARC: the same _dmarc record as for any other provider, starting at p=none.
p=none, quarantine or reject: which one should I use?
Start with p=none: nothing is blocked and you receive the reports. After a few weeks, once all your legitimate mail passes, move to p=quarantine: fakes go to spam. Finish at p=reject: fakes are refused. Staying at p=none forever protects nobody.
My SPF record has more than 10 DNS lookups. Is that a problem?
Yes. Past 10 lookups (include, a, mx, ptr, exists and redirect, counted through every nested include), SPF returns an error. For DMARC it is as if there were no SPF at all, so your real mail may be refused. Remove unused services, replace an include with ip4: ranges when possible, or move the newsletter to a subdomain.

Get your company’s email protected

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 , president of OKTO Solutions · updated