Notification
Go to Home All Tools Compare Glossary Blog Contact

DMARC, SPF & DKIM Email Security Checker

Audit your domain's email authentication records. Prevent domain spoofing, test DMARC enforcement, verify SPF syntax & lookup limits, and inspect MX routes.

Live DNS Inspector RFC 7208 / 7489 / 6376 Google & Yahoo 2024 Ready

Domain Audit Console

DNS PORT 53
e.g., domain.com
s._domainkey

Leave blank to auto-probe common selectors (google, selector1, k1, default, s1, mail).

Quick Example Presets:
2024 Google & Yahoo Inbox Mandates

Gmail and Yahoo require all senders (and strictly enforce for bulk senders delivering 5,000+ daily emails) to publish authenticated SPF and DKIM, configure a valid DMARC policy, maintain forward/reverse DNS, and keep spam complaints under 0.3%. Unauthenticated mail is automatically rejected or routed to spam.

DMARC Required SPF Validated DKIM Cryptography

No Domain Audited Yet

Enter your root domain name or email address above to query live DNS records for SPF syntax, 10-lookup limits, DMARC enforcement policies, DKIM keys, and MX routing.

•
Step-by-Step Guide

How to Audit & Fix Domain Email Deliverability

Protect your transactional emails, sales outbound sequences, and customer notifications from landing in spam folders in 4 simple steps.

1

Enter Your Domain

Type your company domain or sending address (e.g., example.com) to trigger live authoritative DNS lookups across root nameservers.

2

Enforce DMARC Policy

Verify whether your DMARC tag is set to p=reject or p=quarantine. Avoid remaining indefinitely on p=none.

3

Cap SPF at 10 Lookups

Ensure your SPF record does not exceed the RFC 7208 10-DNS-lookup limit to prevent PermError delivery failures.

4

Apply Ready-Made Fixes

Copy our recommended DNS TXT records directly into Cloudflare, GoDaddy, AWS Route 53, or Namecheap to secure your sending.

Protocol Comparison

DMARC vs SPF vs DKIM vs BIMI: How They Work Together

Modern inbox providers (Google, Yahoo, Microsoft) require a layered approach to verify email origin and prevent spoofing.

Protocol Primary Purpose RFC Standard DNS Location Mandatory in 2024?
DMARC Tells receiving servers whether to reject or spam mail that fails SPF/DKIM RFC 7489 _dmarc.yourdomain.com Required
SPF Specifies which IP addresses and mail servers are authorized to send RFC 7208 yourdomain.com (Root TXT) Required
DKIM Cryptographically signs email body & headers to prevent tampering in transit RFC 6376 selector._domainkey.yourdomain.com Required
BIMI Displays official verified company logo next to sender in Gmail and Apple Mail BIMI Group Draft default._bimi.yourdomain.com Optional
Practical Application

When to Use the DMARC, SPF & DKIM Email Security Checker

Common real-world scenarios and planning use cases where this calculator delivers maximum precision.

Outbound Sales & Marketing Campaigns

Verify authentication before launching cold email outreach, sales sequences, or marketing newsletters to prevent messages landing in spam.

Diagnosing Spam & Bounce Delivery Issues

Troubleshoot high bounce rates, SPF softfail warnings, and automatic spam redirection in Gmail, Yahoo, and Outlook inboxes.

2024 Google & Yahoo Mandate Compliance

Ensure your sending domain strictly satisfies Google and Yahoo's required authentication checklist (valid DMARC, SPF, DKIM, and MX).

Onboarding Email & SMTP Providers

Verify DNS TXT records when configuring Google Workspace, Microsoft 365, Zoho Mail, SendGrid, Amazon SES, or Mailchimp.

DNS Migrations & Server IP Changes

Confirm that all SPF includes, DKIM selectors, and DMARC policies remain active after migrating DNS hosts (e.g. to Cloudflare or Route 53).

Stopping Executive Phishing & Spoofing

Enforce DMARC p=reject to permanently block attackers and scammers from impersonating company executives or domain addresses.

Financial Pro Tip

Always monitor your SPF record's DNS lookup count. RFC 7208 strictly limits SPF evaluation to 10 lookups; exceeding 10 causes receiving inboxes to trigger an automatic PermError failure.

Good to know

Questions, answered

Quick answers about how this tool works.

An Email Security Checker inspects public DNS records (DMARC, SPF, DKIM, and MX) published on authoritative nameservers for your domain. It verifies whether your email authentication is properly configured to prevent domain spoofing, ensure messages reach recipient inboxes instead of spam folders, and comply with mailbox provider policies.

Starting February 2024, Google and Yahoo require all senders—especially bulk senders sending 5,000+ messages per day—to configure SPF and DKIM authentication, publish a valid DMARC policy on the sending domain, maintain valid forward and reverse DNS (PTR records), keep user-reported spam rates below 0.3%, and support one-click unsubscribe headers. Non-compliant domains face delivery throttling, spam folder placement, or outright rejection.

A policy of p=none (Monitoring) allows all emails through while generating aggregate reports; it provides zero protection against domain impersonation. A policy of p=quarantine (Soft enforcement) directs failing messages to recipients' spam folders. A policy of p=reject (Full enforcement) instructs receiving servers to discard spoofed emails at the gateway, preventing them from ever reaching users.

RFC 7208 mandates that an SPF evaluation must not generate more than 10 DNS lookups across include:, a, mx, ptr, exists:, and redirect= mechanisms. Exceeding 10 lookups triggers an SPF PermError (Permanent Error) and causes receivers to reject or spam incoming mail. To fix it, remove legacy vendor includes, merge IP ranges using ip4:/ip6: CIDR notation, or use SPF flattening services.

Was this tool helpful?

Be the first to rate DMARC, SPF & DKIM Email Security Checker

Tap a star to rate instantly

What do you need to work out next?

Search 276+ free tools by name, or pick a category below. Every one runs instantly in your browser — no signup, nothing to install.

More Security Tools
AI ADVISOR & COACH

Ask AI Advisor

Ask AI