On this page(8)
Email DNS records, explained
The email DNS records that decide whether your mail is found, trusted, and delivered are five: MX (where your mail is received), SPF (who’s allowed to send for you), DKIM (a tamper-proof signature), DMARC (what to do when checks fail), and PTR (reverse DNS that ties your IP back to your name). Get these right once and they quietly protect every message you send.
Most people meet DNS only when something breaks. An email bounces, a tech-support article says “add a TXT record,” and you paste a string you don’t understand into a box you’ve never opened. It works, you close the tab, and you learn nothing. Let’s fix that — because understanding dns for email deliverability turns a scary chore into a five-minute checklist you’ll never fear again.
Think of DNS as the internet’s phone book, and these five records as the entries that tell the world how to find and trust your email.
The five records that run your email
| Record | What it does | Example (simplified) |
|---|---|---|
| MX | Points to the server that receives mail for your domain | 10 mail.yourdomain.com |
| SPF | Lists the servers allowed to send as your domain | v=spf1 include:_spf.provider.com ~all |
| DKIM | Publishes the key that verifies your signature | selector._domainkey → v=DKIM1; p=... |
| DMARC | Tells receivers what to do on SPF/DKIM failure + reports | v=DMARC1; p=none; rua=mailto:... |
| PTR | Reverse DNS — maps your sending IP back to a hostname | 1.2.3.4 → mail.yourdomain.com |
MX records explained
MX records explained simply: MX (Mail eXchange) records tell the world which server should receive email for your domain. When someone emails [email protected], their server looks up your MX record to find where to deliver it. The number in front (the “priority,” like 10) lets you list backups — lower numbers are tried first. Note: MX is about receiving. It has nothing to do with whether your outbound campaigns land in the inbox — that’s SPF, DKIM, and DMARC’s job.
SPF, DKIM, and DMARC: the trust trio
These three are the authentication records that decide if mailbox providers trust your outbound mail. In one line each: SPF says which servers may send for you, DKIM adds a cryptographic signature proving the message wasn’t altered, and DMARC ties them to your visible From: address and tells receivers what to do on failure. Since Google and Yahoo’s 2024 bulk-sender rules, all three are effectively required. We’ve written a full plain-English guide to setting up SPF, DKIM, and DMARC — this post is the map; that one is the walkthrough.
What is a PTR record?
What is a PTR record? It’s reverse DNS — the opposite of a normal lookup. A normal record turns a name into an IP; a PTR turns your sending IP back into a name. Mailbox providers check it to confirm your sending IP resolves to a legitimate hostname on your domain. A missing or generic PTR (like a raw hosting-provider string) is a quiet trust-killer. Your sending provider or host usually sets this; if you run your own IP, make sure it resolves to a hostname that matches your sending domain.
receive
who can send
signature
policy
reverse DNS
A simple email DNS setup checklist
If you’re doing an email dns setup from scratch, work in this order:
- 1. MX — so you can receive mail (often set by your email host).
- 2. SPF — one TXT record listing every service that sends for you.
- 3. DKIM — publish the key your sending platform gives you.
- 4. DMARC — start at
p=noneto monitor, then tighten. - 5. PTR — confirm reverse DNS with your provider/host.
You don’t need to memorize the syntax — you need to know these five exist and that all of them should be in place. Most deliverability mysteries are just one of these five quietly missing or misconfigured.
How to check your records
Verify everything in two minutes: send a message to a Gmail account, open Show original, and confirm SPF, DKIM, and DMARC read PASS. Use a DNS lookup tool (MXToolbox or similar) to check MX and PTR. Re-check whenever you add a new sending tool — each one usually needs to be added to SPF and signed with DKIM.
DNS set up for you, verified before you send
EmailSendX generates the exact MX, SPF, DKIM, DMARC, and PTR records for your domain and verifies each one passes before your first campaign — so your email is found, trusted, and delivered from day one.
Frequently asked questions
What DNS records are needed for email?
Five: MX (to receive mail), and SPF, DKIM, DMARC, and PTR (to send and be trusted). Also, MX handles incoming; the other four protect your outbound deliverability.
What is an MX record in simple terms?
It points to the server that receives email for your domain. The priority number lets you list backups, with lower numbers tried first. MX only affects receiving, not whether your campaigns reach the inbox.
What is a PTR record and do I need one?
A PTR is reverse DNS that maps your sending IP back to a hostname. Mailbox providers check it to confirm your IP is legitimate, so yes — a missing or generic PTR hurts deliverability.
How do I check my email DNS records?
Send to a Gmail account and open Show original to confirm SPF, DKIM, and DMARC pass; use a DNS lookup tool like MXToolbox to verify MX and PTR.
Ready to try it?
