Reverse DNS Lookup
Punch in an IP or hostname, read the PTR record, and check whether the name points back to the same address.
This reverse DNS lookup takes an IP and hands you the PTR hostname behind it, the record that runs forward DNS in the opposite direction. Give it a hostname instead and it resolves that to an IP first, then digs up the PTR and checks whether that name actually points back to the same address. That last step, forward-confirmed reverse DNS, is the part most people skip, and it is the part that decides whether outbound mail gets trusted. It scores the result, flags private and carrier-grade addresses that will never carry a public PTR, and writes operational notes for mail boxes and log digging. It asks the site resolver and a second public resolver so a stale answer cannot fool you.
Queries run through the PeopleAreGeek lookup service. We log nothing.
Live network utility
Punch in an IP. You get the reverse DNS record behind it. If you hand it a hostname instead, it resolves that to an IP first, then digs up the PTR hostname and checks whether that name actually points back to the same address. Honestly the last bit is the part most people skip. It's the bit that matters for mail servers, for staring at logs, for an abuse report you're about to file.
What reverse DNS means
Forward DNS takes a hostname and hands you an IP. Reverse DNS runs that backwards. You give it an IP, it gives you a hostname, and the thing doing the giving is a PTR record. Here's the catch that trips people up: you don't control that record. Whoever runs the reverse zone for that IP range does, and that's almost always the hosting provider or the ISP. It lives nowhere near the DNS zone you edit for your own domain.
Not every connection needs reverse DNS. Your laptop loading a website? Doesn't care. Servers are a different story. Mail systems tend to want a real PTR on outbound mail boxes, and a security person reading logs at 2am will thank whoever set up sensible hostnames, because raw IPs tell you nothing fast. A missing or generic PTR isn't a crime. It's a clue, and sometimes a loud one.
Forward-confirmed reverse DNS
The setup you actually want is called forward-confirmed reverse DNS, which is a mouthful for a simple idea. The IP gives you a PTR hostname. Then that hostname, looked up the normal way through an A or AAAA record, points right back at the same IP. Does that prove you own anything? No. It just means the forward and reverse stories agree with each other instead of contradicting themselves, and for outbound mail that agreement buys you trust and saves you a headache when something breaks.
When to use this PTR lookup
- You want to know if a mail server IP has a hostname that makes any sense at all.
- Some server IP keeps showing up in your access logs and you'd like to know what it is.
- You just migrated a box and you're checking whether the provider bothered to set up PTR.
- A suspicious IP landed on your desk and you want to eyeball its hostname before you escalate the abuse report.
- Mail is getting flagged or delayed somewhere, and you need to write down why.
Common limitations
Plenty of home and mobile IPs come back with some ugly generic hostname, or with nothing. Cloud servers usually wear a provider-style name until you go in and ask for a custom one. Private addresses like 192.168.x.x or 10.x.x.x have no public reverse DNS, full stop, so don't waste time looking. IPv6 reverse DNS does exist. Whether you get a clean answer though depends entirely on how the provider delegated the reverse zone, and I've seen that go both ways.
Frequently asked questions
Can I create a PTR record in my normal DNS panel?
Usually no, and people get stuck here all the time. The PTR belongs to whoever owns the IP, not you. On a VPS or a dedicated box, dig around the hosting panel for a reverse DNS field, and if there isn't one, just email the provider and ask them to set it.
Does missing reverse DNS hurt SEO?
For a normal web page, no, not really. Where it actually bites is email getting through, the reputation your server carries, and whether your logs read cleanly when you're trying to debug something at speed.
Should the PTR hostname match my website domain?
On a plain web server, eh, it doesn't have to. On a mail server it's a different ask. There the name should be something you chose on purpose, something that doesn't keep changing, and it ought to line up with your forward DNS and the identity your mail sends under.
What is reverse DNS used for?
It turns an IP back into a hostname through a PTR record. Mail servers lean on it when they're deciding whether you're spam. Past that, it's mostly about figuring out who owns an address when you're knee-deep in logs.
Do I need reverse DNS to send email?
In practice, running your own mail server, yeah. A lot of receivers will bounce you outright, or quietly shove you toward spam, if the IP has no PTR or the PTR doesn't match the hostname you're sending as.