Build Your DNS Security Records
Choose your email provider, DMARC enforcement level, and Certificate Authority — your records update instantaneously below.
Why These 3 Records Matter
Publishing SPF and DMARC prevents phishing using your domain name and satisfies Gmail/Yahoo bulk-sender requirements. Adding CAA locks down which authority can issue SSL certificates. Read the full Email Authentication Guide or verify existing records in our DNS Lookup Tool.
1. SPF (@ TXT)
Authorizes your email servers to send mail on behalf of your domain. Never publish more than one SPF TXT record per hostname.
2. DMARC (_dmarc TXT)
Instructs receiving inboxes to monitor, quarantine, or reject emails that fail both SPF and DKIM alignment checks.
3. CAA (@ CAA)
Restricts TLS certificate issuance to your chosen Certificate Authority (for example letsencrypt.org), blocking unauthorized certificates.
Frequently Asked Questions
~all (SoftFail) marks unauthorized senders as suspicious while leaving final delivery decisions to DMARC and spam filters — recommended for active mail domains. -all (HardFail) strictly rejects all unlisted senders, ideal for parked or non-sending domains.
Start with p=none for 2–4 weeks to review aggregate XML reports and confirm all legitimate services pass SPF/DKIM. Then step up to p=quarantine and finally p=reject.
Log in to your DNS provider (such as OVHcloud, Cloudflare, or your registrar's DNS zone editor). Paste SPF at host @ (root) as TXT, DMARC at host _dmarc as TXT, and CAA at host @ as CAA.
Without a CAA record, any publicly trusted Certificate Authority worldwide can theoretically issue an SSL certificate for your domain. CAA limits issuance strictly to the CA(s) you authorize.