Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
SPF, DKIM and DMARC are a set of three settings that guard against email spoofing. Email has the property that anyone can fake the sender simply by claiming a name. The three settings let the receiving side check whether a message is genuine mail from the domain.
How do SPF, DKIM and DMARC work?
Think of a sealed letter in the post. SPF is the sender's list saying only parcels sent from these addresses are genuine. DKIM is the wax seal pressed on the envelope, which shows whether it was opened on the way. DMARC is the rule by which the sender tells the recipient what to do with a parcel whose list or seal does not match.
According to RFC 7208, SPF is a mechanism by which the owner of a domain publishes in DNS the servers allowed to send mail for that domain. The receiving side compares the sender against it. It also provides that you must not register more than one SPF record under the same name, and that more than 10 DNS lookups count as a failure.
DKIM is a mechanism in which the sender signs with a secret key and the receiver checks with a public key in DNS. RFC 6376 defines it. Even when a signature check fails, there is no duty to refuse the message, and the handling is left to the receiver's policy.
DMARC is defined in RFC 9989 of May 2026, which replaces the earlier RFC 7489. It checks whether the domain shown in the From address of the mail matches a domain verified by SPF or DKIM.
There are three policies: none, quarantine, and reject. You can also choose to receive reports on usage, but that is an optional item in RFC 9989. Details of holes in the settings are explained in email authentication flaws.
Why do SPF, DKIM and DMARC matter?
Because they reduce the fake mail that claims your domain and reaches customers and business partners. Fake mail poses as a partner or a company and is used to lead people to viruses or fake login screens. The people harmed are those who receive it, but the trust lost belongs to the company whose name was used.
According to the Ministry of Internal Affairs and Communications' white paper, adoption on JP domains as of December 2025 was about 89.6% for SPF and about 37.2% for DMARC. DMARC has not yet reached half, unlike SPF. For a company that wants to take its anti-spoofing a step further, setting up DMARC is the next task.
Our free URL check reads the SPF and DMARC records. It shows whether the policy is still none or whether nothing is set at all. In an assessment, email authentication settings are also a point we check.
In what order should you set them up?
- List every service you send mail from, including newsletters and contact forms.
- Set up SPF and DKIM for those senders.
- Add DMARC at policy none, and read the reports.
- Move step by step toward quarantine and reject.
For help with the senders list or the pace of tightening, contact us.
Related terms
- WAF: a wall that stops malicious traffic at the entrance
- Vulnerability: a security hole in a program or its settings
Frequently asked questions
Which of the three should I set up first?
A workable order is to list the services you send mail from, set up SPF and DKIM first, and add DMARC last. DMARC works on top of the results of SPF and DKIM.
Is it a problem to leave the DMARC policy at none?
None is a watching stage that does not ask receivers to change how they treat mail. Once you have read the reports and checked your senders, moving step by step to quarantine, which isolates suspicious mail, and then reject, which refuses it, makes it more effective against spoofing.
If I set it wrong, will my own mail stop arriving?
It may. If you tighten the policy while some senders are not yet listed, such as a newsletter service or a contact form, even genuine mail can be refused. Strengthen the policy a little at a time while reading the reports.
Next step
Your domain's state can be read from its SPF and DMARC records with the free URL check, which shows only what is visible from outside. To work out your senders or how fast to tighten the policy, contact us. For preparation against fake mail as a whole, see phishing countermeasures, and for holes in the settings, email authentication flaws.
Frequently asked questions
Which of the three should I set up first?
A workable order is to list the services you send mail from, set up SPF and DKIM first, and add DMARC last. DMARC works on top of the results of SPF and DKIM.
Is it a problem to leave the DMARC policy at none?
None is a watching stage that does not ask receivers to change how they treat mail. Once you have read the reports and checked your senders, moving step by step to quarantine, which isolates suspicious mail, and then reject, which refuses it, makes it more effective against spoofing.
If I set it wrong, will my own mail stop arriving?
It may. If you tighten the policy while some senders are not yet listed, such as a newsletter service or a contact form, even genuine mail can be refused. Strengthen the policy a little at a time while reading the reports.