SPF, DKIM and DMARC checker
Determine whether a third party can send mail on behalf of your domain. The check queries public DNS records only and generates the recommended records.
What each record checks
SPF authenticates the sending server and DKIM signs the message, but neither alone protects the address the recipient sees. That protection depends on a DMARC policy in quarantine or reject mode.
Record
Location
Function
SPF
TXT at the root
Authorises servers that send mail
DKIM
TXT at _domainkey
Signs outgoing messages
DMARC
TXT at _dmarc
Defines the action for unauthenticated messages
Recommended rollout
Publish SPF
Include every service that sends mail for the domain. Only one SPF record may exist.
Microsoft 365
v=spf1 include:spf.protection.outlook.com ~allGoogle Workspace
v=spf1 include:_spf.google.com ~allEnable DKIM
Generate the key in your mail provider's console and publish the record it gives you.
Publish DMARC in monitoring mode
Start with none and review the reports to identify every legitimate sender.
v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.comApply the blocking policy
Move to quarantine and then reject once all legitimate senders are authenticated.
v=DMARC1; p=reject; rua=mailto:dmarc@yourcompany.com
Frequently asked questions
- What is DMARC?
- DMARC is a DNS record that tells receiving servers what to do with mail that fails SPF or DKIM authentication and requests reports on the use of the domain.
- Is SPF enough?
- No. SPF validates the technical envelope sender, not the address visible in the From field. Without a blocking DMARC policy, the domain can still be spoofed.
- Why is my DKIM not found?
- DKIM is published under a selector that cannot be enumerated. The tool queries the most common selectors, so a custom selector may not appear. Confirm with your mail provider.
- Does the check send mail to my domain?
- No. It only queries public DNS records.