When you visit a website, DNS turns its name into an IP address. A PTR record does the opposite: it maps an IP address back to a hostname. Our PTR Record Lookup shows you that hostname for any IPv4 or IPv6 address.
How to check a PTR record
- Enter an IP address, like 8.8.8.8. A domain works too; we resolve it first.
- Press Lookup.
- See the PTR hostname and the reverse zone name.
Why PTR records matter for email
This is where reverse DNS really earns its keep. Many mail servers check that the IP sending an email has a PTR record, and that it looks sensible. If it's missing, or set to something generic, your emails are far more likely to land in spam or be rejected outright.
Who sets the PTR record?
Not you, usually. The PTR record belongs to whoever owns the IP address, which is normally your hosting or internet provider. Most VPS dashboards have a "reverse DNS" setting, or support can set it for you.
Example: why your emails land in spam
You set up a small VPS to send order confirmations from your shop. Customers start saying they never got the emails. A PTR lookup on your server's IP shows a generic hostname like ip-203-0-113-7.provider.net. Many mail providers treat that as a sign of a home or throwaway server. Setting the PTR to mail.yourshop.com, together with proper SPF and DKIM records, usually fixes deliverability.
PTR, A and MX records: what's the difference?
- A record: name to IPv4 address (yourshop.com → 203.0.113.7).
- AAAA record: name to IPv6 address.
- MX record: which server receives email for a domain.
- PTR record: IP address back to a name (203.0.113.7 → mail.yourshop.com).
Troubleshooting
- "No PTR record found": the IP owner hasn't set one. Ask your provider.
- PTR doesn't match your domain: for mail servers, it should match the hostname your server uses when sending.
How reverse DNS works behind the scenes
Normal DNS answers the question "which IP address does this name point to?" Reverse DNS answers the opposite: "which name belongs to this IP address?" To make that possible, the internet keeps a special area of DNS where IP addresses are written backwards. The address 8.8.8.8 becomes 8.8.8.8.in-addr.arpa, and the PTR record stored there holds the hostname, in this case dns.google.
IPv6 works the same way, only longer: every hexadecimal digit of the address is reversed and placed under ip6.arpa. You don't need to build these names yourself. The tool shows the reverse zone so you can see exactly what was looked up.
Forward-confirmed reverse DNS (the check mail servers love)
Many mail servers go one step further than simply checking that a PTR record exists. They take the hostname from the PTR record, look it up the normal way, and confirm it points back to the same IP. When both directions match, it's called forward-confirmed reverse DNS, and it's a strong sign the server is set up properly rather than being a random infected machine.
So if your PTR record says mail.yourshop.com, make sure mail.yourshop.com has an A record pointing to that same IP address. Get that pair right and a lot of delivery problems quietly disappear.
A quick checklist for a self-hosted mail server
- Set the PTR record for your server's IP to a real hostname, such as mail.yourdomain.com. Your hosting provider does this.
- Create an A record for that hostname pointing back to the same IP.
- Make sure your mail server introduces itself with that same hostname.
- Add SPF, DKIM and DMARC records for your domain.
- Send a test message to a Gmail or Outlook address and check whether it lands in the inbox.
Common mistakes
- Trying to set the PTR record in your domain's DNS panel. It doesn't go there. It belongs to whoever owns the IP, which is almost always your host.
- Using a generic hostname. Something like server123.hostingcompany.net works technically but looks less trustworthy to mail filters than a name on your own domain.
- Forgetting IPv6. If your server sends mail over IPv6, that address needs its own PTR record too.
Using reverse DNS to understand your logs
If you run a website, your server logs are full of IP addresses. A PTR lookup can turn some of them into something meaningful. An address that resolves to a name ending in googlebot.com is likely Google's crawler; one that resolves to a home broadband provider is probably a regular visitor. It's a quick way to spot unusual traffic without any special software.
Other uses
- Identifying which company an IP in your logs belongs to
- Troubleshooting network and mail problems
- Checking a server setup after a migration