Every server that sends email, and most that host anything, has a public IP address. This tool tells you what the internet says about one: its reverse DNS name, whether that name points back, and which regional internet registry allocated the block it belongs to. It is the lookup behind the Look up buttons in the email header analyzer.
What you get
- Reverse DNS: the PTR record for the address, the name it gives, and whether that name's own A or AAAA record points back to the same address (forward-confirmed reverse DNS). Both lookups go through our own validating resolver.
- The allocating registry: ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC, read from the bootstrap files the internet's numbering authority publishes. We keep a copy of those files on our servers, so nothing about your lookup leaves us for this part.
- The announcing network: the AS number, holder and prefix from our routing data.
- The address itself: its version and scope.
Why reverse DNS matters for email
Mail servers check reverse DNS on every incoming connection. A sending server whose address has no PTR record, or one whose name doesn't point back, is a common reason for mail to be rejected or sent to spam. Reverse DNS is set by whoever runs the network (your hosting company, cloud provider or internet provider), not in your own domain's DNS, so the fix starts with them. The guide linked from the finding explains how.
Reading the result
A name that points back is what you want for any server that sends mail: it shows that whoever runs the network agrees the address belongs to that host. A name that doesn't point back usually means the PTR was set long ago and the host name has since moved, or that the network owner set a generic name such as one built from the address itself. No name at all is common for home connections and for many cloud addresses until someone sets one. If the reverse lookup itself doesn't answer, nothing is charged and you can try again in a minute; if only the check back fails, the result is marked partial and says so.
Private and reserved addresses
Addresses such as 10.0.0.1, 192.168.1.1 or 127.0.0.1 live only inside a network; nothing public is known about them. You often see them in email headers for hops inside a company. We refuse them for free and name the range, so you don't pay for an answer that can't exist. The same goes for documentation, link-local, shared (carrier-grade NAT) and other reserved ranges. Only IP addresses are accepted; for names, use the DNS lookup.
Privacy
An IP address can belong to a person's home connection, so we keep as little as we can. Your usage history records only the block the address belongs to (the first three parts of an IPv4 address, the first three groups of an IPv6 address), never the address itself. Results are cached for an hour, for your account only, and are never shared. We don't use location or ownership databases, and nothing is sent to the regional registries.
The announcing network
The result also names the network that announces the address to the rest of the internet: its AS number, the holder's name and country, and the prefix the address sits in. This comes from our own copy of the global routing table, built once a day from public route collector data, so no third party sees your lookup. When several networks announce the same prefix the result says so, and when no network announces it you get a finding that explains what that means. For the full list of what a network announces, use the ASN lookup.
Routing data: RIPE NCC RIS. AS names: RIPE NCC. Allocations: ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC statistics.
We still don't show the owning organisation's contacts: they live in the regional registries' own records, and asking them would let them see which addresses you look up.
Using it with headers
Paste a message's headers into the email header analyzer. Signed in, each public address in the hop table has a Look up button; "Look up all" runs every one, at 1 credit each. Only the address is sent, never the headers.