SPF & DMARC Record Generator
Generate cryptographically validated, RFC-compliant TXT DNS records to meet 2026 Gmail and Yahoo email authentication requirements.
1. Domain & Email Providers
SPF TXT Record
@ (or example.com) • Type: TXT • TTL: 3600DMARC TXT Record
_dmarc (or _dmarc.example.com) • Type: TXT • TTL: 3600- Log in to your DNS provider (Cloudflare, GoDaddy, Namecheap, Route 53, cPanel).
- Add a new TXT record for SPF with Name:
@and the value generated above. - Add a second TXT record for DMARC with Name:
_dmarcand the generated value. - Allow 15–60 minutes for worldwide DNS propagation.
Understanding SPF & DMARC: The Pillars of Outbound Email Deliverability
Sender Policy Framework (SPF) is an email authentication method designed to detect forging sender addresses during the delivery of the email. SPF allows the receiving mail server to check that incoming mail from a domain comes from a host authorized by that domain's administrators. The list of authorized sending hosts for a domain is published in the Domain Name System (DNS) records for that domain in the form of a specially formatted TXT record.
DMARC (Domain-based Message Authentication, Reporting, and Conformance) builds upon SPF and DKIM. While SPF checks whether the sending IP is authorized, it doesn't specify what the receiving mailbox provider should do if an unauthorized email arrives. DMARC solves this by enabling the domain owner to publish a strict policy:
- `p=none`: Monitor mode. Reports are generated and sent to your `rua` email, but unauthorized emails are still delivered to inboxes.
- `p=quarantine`: Suspicious emails that fail authentication are routed directly into the recipient's Spam/Junk folder.
- `p=reject`: Maximum security. Unauthenticated emails are rejected and blocked at the SMTP handshake level.
Need an end-to-end deliverability infrastructure? Check our complete SPF, DKIM, and DMARC Implementation Guide.