A domain, a web address or an email address all work.

This email did not come from you. Your customer cannot tell.

Your domain is the part of your email address after the @, such as example.com. Anyone can put it in the From line of an email, like a return address on an envelope. They do not need your password.

Three short public notes on your domain, called SPF, DKIM and DMARC, help mail services tell your email from fakes. Without a DMARC note, each mail service decides alone what to do with a fake.

Subject: Your invoice is overdue

From: Billing billing@example.com

10:12

to me

Pay today to avoid a late fee. The bank details have changed: use the account in the attached PDF.

Attachment: invoice-4471.pdf86 KB

The From line says example.com, but example.com did not send it. A DMARC note can ask mail services to refuse fakes or send them to spam. Unless a note asks for one of the two, nothing asks them to act on this one.

And your real email starts landing in spam.

Gmail, Yahoo and Outlook.com publish rules for anyone who sends them email. They refuse email that breaks the rules, or send it to spam.

Every rule side by side, with the error each provider sends back

How the check works

  1. Type your email address or website

    You can paste it too. The check takes your domain from it.

  2. Read the answer

    First comes one sentence: can someone else send email as your domain? Then each note on your domain, in everyday words.

  3. Copy the fix

    Most fixes are a note to copy, with the type, host and value your domain settings ask for. With no DMARC note, or one that asks for nothing, the fix takes three steps. The last one asks mail services to refuse fakes.

Spoofable
Anyone can send email as your domain.
Partly protected
Fakes are only asked to go to spam, or names under your domain, like shop.example.com, are still open.
Protected
Your domain is protected from fake email at mail services that check DMARC.
Can’t tell
The check could not get a clear answer for your domain, so it does not say yet.

Does someone else look after your domain, like whoever built your website? Copy all fixes in one go and send them to that person.

After you make the changes, send a real email to the email test and see whether SPF, DKIM and DMARC passed when it arrived.

What the check looks at

Four short public notes on your domain, called records. Mail services read them, and so can anyone passing, like a notice in your shop window. Only you, or whoever looks after your domain, can change them.

  • MX

    example.com

    Tells other mail services where to deliver email sent to your domain: its delivery address for email. A domain that receives no email can say so with a special note, called a null MX.

  • SPF

    example.com

    A list of the services allowed to send email for your domain, such as your email provider or newsletter tool. Mail services may look things up for it at most 10 times. A list that needs more counts as broken, and SPF then stops helping your email.

  • DKIM

    selector._domainkey.example.com

    Your email service puts a hidden seal on each message it sends. Mail services check it with a key that sits on your domain, under a name your provider picks. DKIM does not hide what your email says.

  • DMARC

    _dmarc.example.com

    Some email shows your domain in the From line but passes neither SPF nor DKIM for your domain. DMARC asks mail services to send that email to spam or refuse it. Set to none, it asks for nothing.

The check also looks for two notes about email sent to you. One can ask other mail services to deliver it only over an encrypted connection (MTA-STS). The other tells them where to report when an encrypted connection fails (TLS-RPT).

Nothing to take on trust.

  • Runs in your browser

    Your browser asks public services for your domain’s notes, over a secure connection. This site never receives the domain you check.

  • No account, no cookies

    The domains you check are not stored, and this site uses no tools that track visitors. Your browser can show you where each request goes.

  • Every rule has a source

    Each rule behind the answer names the standard or the provider page it comes from. See all the rules.

  • Every guide is dated

    Each guide shows the day it was last checked against its sources.

What the public services and the host of this site can see

Questions

Short answers about how the check works and what it cannot see.

Not answered here? Read the guides.

Does the check send an email?

No. It only reads public notes on your domain. It sends nothing to your domain or your inbox.

Can I check a domain I do not own?

Yes. These notes are public. Someone faking your email can read yours the same way.

Why can’t it find my DKIM seal?

Your provider files the key for your seal under a name it picks, called a selector. There is no public list of those names, so the check tries the ones common providers use.

If yours uses another, open an email you sent and look at its technical details. Find the s= value in the line that starts with DKIM-Signature, and type it in. Or send an email to the email test, which finds the selector for you.

I fixed my note. Why do I still see the old one?

The public services keep each answer for a while. A changed note can show its old version until that time (TTL) runs out.

A new note can stay hidden for a while too, because the services also remember that it was missing. Your domain settings set both times. Wait that long, then check again.

If everything passes, will my email reach the inbox?

Passing means mail services can confirm that your email is yours. Reaching the inbox also depends on your history as a sender and on what you send. These notes show neither.

Find out if someone can send email as you.

Check my domain

Check my domain