Cold Email Reverse DNS (PTR Records): The Silent Deliverability Signal

By Puzzle Inbox Team · Apr 24, 2026 · 6 min read

Reverse DNS maps an IP address back to a domain name. Missing or mismatched PTR records hurt cold email deliverability in ways most senders never diagnose.

What Reverse DNS (PTR) Is

Regular DNS maps a domain name to an IP address (A record). Reverse DNS — also called PTR records — maps an IP address back to a domain name. When your cold email server connects to Gmail or Outlook to deliver a message, the receiving server does a reverse DNS lookup on the sending IP. The result is one of the signals the receiving server uses to decide whether your email lands in inbox, spam, or gets rejected entirely.

Why PTR Records Matter for Cold Email

A missing or mismatched PTR record is a classic spammer signal. Legitimate mail servers have properly configured reverse DNS. Spam operations running from cheap VPSs often skip PTR configuration or leave generic hostnames (like ec2-12-34-56-78.compute.amazonaws.com). Receiving mail servers use this to filter suspicious senders.

For cold email operators, PTR record status depends on your infrastructure:

• Google Workspace inboxes: PTR records are Google's responsibility — properly configured for all Google IPs. No action needed.
• Microsoft 365 inboxes: PTR records are Microsoft's responsibility. Properly configured. No action needed.
• Custom SMTP / dedicated IPs: PTR records are your responsibility. Most commonly misconfigured in cold email.
• Shared SMTP: PTR records are the provider's responsibility. Quality varies.

How to Check PTR Records

Use MXToolbox reverse lookup tool. Enter the IP address your cold email is sending from. You should see:

• A PTR record exists
• The hostname it resolves to matches your sending domain pattern
• Forward-confirmed reverse DNS (FCrDNS) passes — the hostname resolves back to the same IP

If any of these fail, deliverability will suffer on any receiving server that uses PTR as a spam signal (most of them).

The FCrDNS Requirement

Forward-confirmed reverse DNS is a two-step verification:

1. IP 1.2.3.4 has PTR record pointing to mail.yourdomain.com
2. mail.yourdomain.com A record resolves back to 1.2.3.4

Both must match for FCrDNS to pass. Gmail, Outlook, and most major providers require FCrDNS for optimal deliverability. One-way PTR (without the forward match) is treated as suspicious.

How to Fix PTR Records for Cold Email

For custom SMTP / dedicated IP setups:

1. Contact your hosting provider / IP owner: PTR records are set by the entity that owns the IP block, not by your DNS provider. Contact AWS, Linode, DigitalOcean, or whoever hosts your sending IPs.
2. Request PTR configuration pointing to a hostname you control (e.g., mail.yourcoldomain.com)
3. Set matching A record in your DNS pointing that hostname back to the IP
4. Verify via MXToolbox reverse lookup — both directions should resolve correctly

Why Shared SMTP Providers Often Have PTR Problems

Shared SMTP providers host many senders on the same IPs. The PTR record for the shared IP points to the provider's hostname, not your domain. This is the opposite of what you want — receiving servers see your emails coming from an IP whose reverse DNS is smtp-relay.budgetprovider.com. That pattern matches thousands of other senders, many of whom are spammers.

This is one of the core reasons shared SMTP cold email underperforms dedicated Google Workspace or Outlook 365 infrastructure.

PTR Records for Google Workspace Cold Email

If you use Google Workspace inboxes (directly or through providers like Puzzle Inbox), Google handles PTR configuration. Every Google Workspace sending IP has proper PTR records pointing to Google-owned hostnames. No action required on your end.

This is one of the underappreciated reasons Google Workspace inboxes have superior cold email deliverability — the PTR infrastructure is globally optimized and has been for decades.