SPF & DMARC Checker
Instantly verify your domain's TXT, SPF, and DMARC records to ensure email deliverability and protect against spoofing.
Secure Processing. No data is permanently stored.
Analyzing Domain Security...
Please wait while we request DNS zones and parse the records.
Record Details
About the SERPInsight SPF & DMARC Checker
Email deliverability is intrinsically tied to domain reputation. Proper SPF (Sender Policy Framework) and DMARC (Domain-based Message Authentication, Reporting, and Conformance) setups prevent malicious actors from sending emails on your behalf.
Developed by SERPInsight, this free utility securely queries global DNS networks to read your TXT strings, validating proper syntax for crucial email authentication protocols.
How it works
-
1
Input Domain
Type or paste the root domain (e.g., yoursite.com) into the tool. Subdomains usually inherit root records, but explicit checks may be required.
-
2
Query DNS Zones
The system bypasses browser cache, fetching live DNS TXT and specific _dmarc records directly from nameservers.
-
3
Parse & Validate
Our engine filters through generic verification strings to isolate, highlight, and validate the syntax of v=spf1 and v=DMARC1 records.
Understanding the Data
Text (TXT) records are versatile DNS entries used to verify domain ownership (like Google Search Console) and establish foundational security protocols.
Sender Policy Framework specifies which mail servers are permitted to send email on behalf of your domain, minimizing the chance of spoofing.
DMARC instructs receiving servers on what to do if an email fails SPF/DKIM checks (e.g., quarantine or reject), providing ultimate brand protection.
Optimization & Security Guide
Key Concepts
- Hard Fail vs. Soft Fail: In SPF,
-all(hard fail) immediately rejects unauthorized IP emails, while~all(soft fail) marks them as spam. - DMARC Policies: Start DMARC with
p=none(monitoring only) before moving top=quarantineorp=rejectto avoid losing legitimate emails. - The 10 Lookup Limit: SPF records inherently limit internal DNS lookups to 10. Exceeding this causes a "PermError" leading to delivery failures.
Best Practices
- Consolidate SPF: Never have multiple SPF records. Combine all authorized senders (Mailchimp, Google, Outlook) into a single
v=spf1string. - Audit Third Parties: Regularly check your SPF includes. Remove legacy IP addresses or defunct services that pose a security risk.
- Monitor Reports: Include an
rua=mailto:tag in your DMARC string to receive daily aggregated threat reports.
Frequently Asked Questions
Why does the tool show my SPF is missing when I added it?
What happens if I have multiple SPF records?
v=spf1 invalidates all of them, resulting in a "PermError". Receiving servers will treat it as if you have no SPF record at all. You must merge them into a single record.
Is DMARC strictly necessary for SEO?
Why use SERPInsight?
Professional-grade tools for experts.
Fast Performance
Our backend architecture queries global DNS nodes instantly, delivering exact TXT records without lag.
Reliable Accuracy
We utilize advanced parsing techniques to isolate correct SPF/DMARC syntax from general domain verification strings.
Privacy First
Your DNS checks are stateless. We do not store historical domain checks or log the health of your email servers.
Clean UX
Instantly filter your results by record type or export the complete DNS zone readout via CSV for IT reviews.