Skip to content
DMARC Pulse

PTR lookup

Reverse DNS Lookup: check the PTR record of an IP or domain

Enter an IP address or a domain to find its PTR record and confirm the name resolves back to the same address. Many receiving mail servers run this same check.

A domain’s A record often points to its website. To check a mail server, enter the IP that sends your email.

Example result

Sample data, not a live check. Run the tool above to see your own result.

Result for

203.0.113.25

Looks good

iprev=pass
203.0.113.25 25.113.0.203.in-addr.arpa
mail-out.acme.example
203.0.113.25
Confirmed

What we found

Reverse DNS is confirmed for 203.0.113.25

The PTR name resolves back to the same address, so a receiving server that runs this check gets a pass. It’s one signal among many: it doesn’t authenticate your email the way SPF, DKIM and DMARC do, and it doesn’t guarantee delivery.

What to do with the result

The PTR name resolves back to the same IP

The label iprev=pass (iprev is this check’s name in mail headers) means the name in this IP’s PTR record lists the same IP in its A or AAAA record. The result covers this one address.

  1. Repeat the lookup for every IP that sends your mail, IPv6 included.
  2. On a server you run, announce this host name in EHLO, the greeting sent on connecting. RFC 5321, section 2.3.5, expects a name that resolves to an address.

Caution: if that name publishes its own SPF record, confirm it authorizes this IP. Receivers may also run SPF on the EHLO name (RFC 7208, section 2.3).

The IP has no PTR record

The label iprev=permerror means the address publishes no name to confirm. Gmail can rate-limit this IP (421 4.7.0) or block its mail (550 5.7.25, “the sending IP address doesn’t have a PTR record”).

  1. Choose a host name used only by this server, such as smtp1.example.com, and create its A or AAAA record with this IP. AWS requires that A record first for an Elastic IP. Avoid an alias (CNAME): RFC 1912, section 2.1, rules it out as a PTR target.
  2. Ask whoever controls the IP to set the PTR to that name.
  3. Check again after 15 minutes, the time we keep a result.

The PTR exists, but its name does not lead back to the IP

The label iprev=fail has two forms. “Mismatch” means the name resolves to other addresses. “Does not resolve” means it has no record for this address type (A for IPv4, AAAA for IPv6). Gmail’s 5.7.25 error covers this too.

  • If the name is yours, add this IP.
  • If your provider set a default name, give your own host name an A or AAAA record with this IP, then ask for a PTR to that name.

Caution: replace an address only when nothing uses it. A new IP on an MX host (one that receives the domain’s mail) can get inbound mail (RFC 5321, section 5.1). If SPF lists the name with a, that IP becomes authorized to send (RFC 7208, section 5.3).

You entered a domain instead of a sending IP

A domain lookup reads only the A and AAAA records of that exact name, up to four addresses. These usually serve a website, where a PTR problem needs no action, so the result reads “Works, with things to improve”. “This domain has no IP address to look up” means neither record exists.

  1. Paste the headers of a message you sent to another provider into the Email Header Analyzer.
  2. Under Delivery path, copy the From IP of the first hop that provider received.
  3. Enter that IP here.

If a listed address also sends your mail, follow the matching case on this page.

The check did not finish, or the address is private

“We could not finish checking” and the “No answer” status mean a DNS query failed, so the result says nothing about the record. We keep each result for 15 minutes. Look up again after that. If it repeats, run dig -x 203.0.113.10 with your IP from another network, then dig A smtp1.example.com with the name it returns (AAAA for IPv6). If you entered a domain, run the same dig A and dig AAAA on it. A SERVFAIL error or a timeout points to the DNS servers of the zone that query went to. Contact whoever runs them.

“Private address” means a range public networks do not route (RFC 1918, section 3) or a reserved one. You likely copied an internal IP, or the server sits behind NAT (address translation). Enter its public sending IP.

Explained

What reverse DNS is

Normal DNS turns a name into an IP address. Reverse DNS does the opposite: it asks which name belongs to an IP. The answer is a PTR record, published under a name built from the address: 203.0.113.10 becomes 10.113.0.203.in-addr.arpa (RFC 1035), and IPv6 addresses use their hexadecimal digits in reverse order under ip6.arpa (RFC 3596).

Why mail servers check it

A receiving mail server knows the IP that connected to it. Many then look up that IP’s PTR record, look up the name they find and check that the answer contains the same IP. This is forward-confirmed reverse DNS (FCrDNS). RFC 8601 names the check iprev, the name it carries in Authentication-Results headers.

SMTP doesn’t require a PTR record, but it lets each server refuse mail for its own operational reasons (RFC 5321), and RFC 1912 warns that PTR and A records that don’t match can cost you Internet services. Gmail requires every sending IP to have a PTR record whose name resolves back to that IP.

A match is a basic signal. It doesn’t guarantee delivery and it doesn’t prove who sent a message: that’s the job of SPF, DKIM and DMARC. RFC 8601 itself advises against using this check for authentication or security.

Who sets the PTR record

A PTR record lives in the reverse zone of the IP address, not in your domain’s DNS zone. Only whoever controls that address can change it, usually your hosting provider, cloud provider or ISP.

  1. Look for a “reverse DNS” setting in your provider’s panel, or open a support ticket.
  2. Point the PTR at the host name your server uses.
  3. Make sure that host name has an A or AAAA record with the same IP. That record does live in the DNS of the name’s domain.

Frequently asked questions

What is a PTR record?
A PTR (pointer) record maps an IP address to a host name, the reverse of an A or AAAA record. It is stored under in-addr.arpa for IPv4 and ip6.arpa for IPv6.
How do I set or change a PTR record?
Ask whoever controls the IP address, usually your hosting provider, cloud provider or ISP. Many offer a “reverse DNS” field in their panel; others do it by support ticket. You can’t set it in your domain’s DNS.
What does forward-confirmed reverse DNS mean?
The IP has a PTR record, and the name in that record resolves back to the same IP. RFC 8601 calls this check iprev: it passes when the IP is among the addresses the name returns.
Can a missing PTR record stop my email from being delivered?
It can. Gmail requires a PTR record on every sending IP, and other receivers may refuse or filter mail from an address without one. A correct record doesn’t guarantee delivery, though: it is one of several checks.
Does the PTR name have to match my domain?
No. The check only asks whether the name resolves back to the IP. On a shared sending service the PTR names the provider, which is normal. On your own server, use a host name under a domain you control.
Why does my domain show no PTR record?
A domain’s A record usually points to its website, and web servers often have no PTR record, which has no effect on your email. Enter the IP that actually sends your mail: you can find it in the Received headers of a message you sent, or ask your email provider.

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.

Related tools