Check SPF, DKIM, DMARC and MTA-STS to see if your domain can be spoofed and whether your email will reach the inbox
Run a complete audit to check performance, mobile-friendliness, meta tags, and more.
Run Free Website AuditEmail was designed without a way to prove who sent a message, which is why anyone can forge the “From” address of your domain. Four DNS-based standards close that gap. SPF lists the servers allowed to send for your domain. DKIM adds a cryptographic signature that receivers verify with a public key you publish. DMARC ties the two together, tells receivers what to do with mail that fails, and sends you reports. MTA-STS protects mail on its way to you by requiring encrypted delivery. This tool reads all of them, follows SPF includes to count the DNS lookups receivers will make, inspects DKIM key strength, checks that DMARC reporting addresses are authorised, and downloads your MTA-STS policy to confirm it matches your real mail servers. Each result comes with plain-language fixes and, when a record is missing, a starting record you can copy.
SPF limits the DNS lookups a receiver performs to 10 to prevent abuse. Every include, a, mx, exists, ptr and redirect counts, including those inside the records you include. Go over, and receivers treat SPF as a permanent error, so legitimate mail can fail. Remove services you no longer use.
DKIM records live at a name that includes a selector chosen by your email provider, and DNS cannot list them. We try about 35 common selectors. If yours is different, enter it under Advanced, or look at the DKIM-Signature header of an email you sent.
Start with p=none and a rua address to collect reports, fix any legitimate senders that fail, then move to quarantine and finally reject. Only quarantine and reject actually stop spoofed mail.
It is optional but valuable. Without it, an attacker on the network can strip encryption from mail sent to you. It needs a DNS record and a small policy file served over HTTPS at mta-sts.yourdomain. Start in testing mode, watch TLS-RPT reports, then switch to enforce.
Publish SPF v=spf1 -all, a DMARC record with p=reject, and a null MX. That stops criminals using it for phishing, and this tool will treat the setup as complete.
The core Simple Mail Transfer Protocol (SMTP) underlying global email was originally designed without built-in mechanisms to verify sender identity. As a result, malicious actors can easily forge the "From" address of any domain, giving rise to domain spoofing, business email compromise (BEC), and phishing attacks.
To bridge this vulnerability, modern mail systems rely on four open, DNS-based authentication standards: SPF, DKIM, DMARC, and MTA-STS. When properly deployed, these protocols verify sender legitimacy, protect email in transit, and instruct recipient servers how to handle unauthorized messages.
This utility—combining a DNS Authentication Parser, a Recursive SPF Lookup Counter, a Cryptographic DKIM Inspector, and an MTA-STS Policy Downloader—delivers a complete, plain-language audit of your domain’s email security posture.
Securing your domain's outgoing and incoming email traffic requires a defense-in-depth architecture. Each of the four DNS-based standards fulfills a distinct operational role:
┌──────────────────────────────────────────────┐
│ Email Authentication Architecture │
└──────────────────────┬───────────────────────┘
│
┌─────────────────────────────────┼─────────────────────────────────┐
│ │ │
┌───────┴───────────────┐ ┌───────┴───────────────┐ ┌───────┴───────────────┐
│ SPF Protocol │ │ DKIM Signature │ │ DMARC Governance │
└───────┬───────────────┘ └───────┬───────────────┘ └───────┬───────────────┘
│ │ │
• Authorized IP Lists • Cryptographic Public Key • Policy Alignment (p=reject)
• Strict 10-Lookup Limit • 1024-bit / 2048-bit RSA • Aggregate RUA/RUF Reports
What It Does: A DNS TXT record that lists the specific IP addresses, subnets, and third-party mail services (e.g., Google Workspace, Mailchimp) authorized to send email on behalf of your domain.
The 10-DNS-Lookup Rule: The official SPF specification (RFC 7208) enforces a strict limit of 10 mechanisms that require DNS lookups (such as include:, a, mx, ptr). Exceeding 10 lookups causes SPF validation to fail with a PermError, leaving your messages unprotected.
What It Does: Uses public-key cryptography to append a digital signature to the headers of outgoing emails.
Validation: Recipient mail servers query your domain’s DNS to retrieve your public key (published at a specific selector path) and verify that the message content was not tampered with during transit. The tool checks for cryptographic key strength (adviosing 2048-bit keys over outdated 1024-bit keys).
What It Does: Synthesizes SPF and DKIM by checking for identifier alignment (ensuring the "From" header matches the domain authenticated by SPF and DKIM).
Policy Enforcement & Reporting: Tells receiving mail servers what to do if an unauthenticated message arrives (p=none for monitoring, p=quarantine for spam folder routing, or p=reject to block delivery). DMARC also routes aggregate (rua) and forensic (ruf) XML reports back to your designated security mailboxes.
What It Does: Protects incoming email in transit by requiring receiving mail servers to negotiate encrypted TLS connections with valid digital certificates.
Validation: Enforces encrypted delivery via a policy file hosted at [https://mta-sts.yourdomain.com/.well-known/mta-sts.txt](https://mta-sts.yourdomain.com/.well-known/mta-sts.txt), effectively preventing Man-in-the-Middle (MITM) and downgrade attacks.

This security tool executes code-level inspections across all four protocols to pinpoint hidden authentication breakdowns.
| Feature | Technical Implementation | Administrative Benefit |
|---|---|---|
| Recursive SPF Lookup Counter | Follows nested include: directives to count total DNS lookups. |
Prevents silent PermError failures caused by exceeding the 10-lookup cap. |
| DKIM Key Inspector | Inspects specific DKIM selectors and measures public key bit length. | Highlights weak or legacy 1024-bit keys that need rotation to 2048-bit. |
| DMARC Alignment & RUA Audit | Validates DMARC syntax and verifies third-party report authorization. | Ensures aggregate reports arrive safely without external domain rejection. |
| MTA-STS Policy Downloader | Fetches live HTTPS policy files and compares MX records against policies. | Guarantees inbound email transport security and certificate matching. |
| One-Click Copy Starters | Generates compliant starting TXT records for missing configurations. | Simplifies record creation for immediate registrar deployment. |

Type your apex domain name (e.g., yourdomain.com) into the tool and optionally enter your DKIM selector (e.g., google or default).
Check your total SPF DNS lookups. If the count exceeds 10, consolidate nested includes or deploy SPF flattening techniques to keep the count within standard limits.
Examine your DMARC record. If your policy is currently set to p=none, use the generated reports to verify legitimate mail streams before escalating your policy to p=quarantine or p=reject to stop spoofing completely.
Verify that your MTA-STS TXT record (_mta-sts.yourdomain.com) and HTTPS policy file match your current MX server configuration to prevent SMTP transport interception.

Target a p=reject DMARC Policy: A p=none policy only monitors traffic; it does not block spammers from spoofing your domain. Transition to p=quarantine and ultimately p=reject for absolute spoofing prevention.
Rotate DKIM Keys Annually: Regularly rotate your DKIM selector keys and enforce minimum key lengths of 2048 bits to prevent cryptographic key cracking.
Authorize External Reporting Destinations: When sending DMARC reports (rua) to an external domain, ensure the receiving domain publishes a valid DMARC authorization record (yourdomain.com._report._dmarc.externaldomain.com).
SPF alone is rarely sufficient for inbox placement. If your DKIM key is missing or your DMARC record lacks alignment (or has a p=none monitoring policy), receiving algorithms like Google and Yahoo may still classify your messages as unverified or suspicious.
When an SPF record requires more than 10 DNS lookups to evaluate, receiving mail servers stop evaluating the record and return an SPF PermError. Under strict DMARC policies, a PermError causes SPF authentication to fail.

No. SPF, DKIM, and DMARC verify sender identity and message integrity at the application layer. MTA-STS works at the transport layer, ensuring that incoming connections between mail servers use secure, encrypted TLS pathways
Email authentication is no longer optional. Modern inbox providers actively deprioritize or reject mail from domains lacking robust SPF, DKIM, and DMARC authentication.
For Total Spoofing Protection: Combine an optimized SPF record (under 10 lookups) with 2048-bit DKIM keys and enforce a strict DMARC p=reject policy.
For Secure Transport: Deploy MTA-STS to enforce TLS encryption and protect your inbound mail streams from transport interception.
Use the Email Authentication & Security Diagnostic Tool above to uncover vulnerabilities, copy validated starting records, and protect your domain's brand reputation today!