PTR Record Lookup — Reverse DNS for IPv4

Forward DNS starts at a hostname and ends at an IP. Reverse DNS starts at an IP and ends at a hostname. PTR records live in special reverse zones under in-addr.arpa for IPv4. Operators delegate those zones to the organization that owns the address block.

Matching forward and reverse — sometimes called FCrDNS — means the PTR hostname resolves back to the same IP via A record. Mail providers weigh this heavily. Our tool shows PTR only; confirm forward resolution separately with an A lookup on each returned hostname.

Receiving mail servers use PTR as a lightweight identity signal. Missing PTR suggests dynamic residential space or neglected server hygiene. Generic auto-generated names may score poorly in spam filters even when technically present.

Outbound SMTP IPs should PTR to a name that reflects your domain — for example mail.example.com — and that name should resolve forward to the same IP. Fix PTR through your hosting or ISP who controls the reverse zone, not through your forward DNS host alone.

The ptrQuery value is the fully qualified domain name sent to DNS resolvers — octets reversed plus in-addr.arpa. Seeing the exact query helps when opening tickets with network providers or comparing results across tools.

IPv6 reverse uses ip6.arpa with nibbles reversed; this page focuses on IPv4 PTR as implemented in our handler. Enter only valid four-octet public addresses.

Some configurations publish several PTR names for one address. Shared hosting and legacy balance setups do this. Receivers may pick the first answer or apply heuristics; best practice is one meaningful PTR per sending IP.

If you see unexpected names on infrastructure you control, investigate delegation changes or stale reverse DNS after IP reassignment.

Cloud providers assign reverse names automatically unless you request custom PTR for eligible addresses. Elastic IPs often support custom PTR through the provider console after you prove domain ownership.

Residential and mobile IPs frequently lack useful PTR. Do not attempt bulk mail from those ranges; focus PTR configuration on dedicated server and relay addresses.

SIEM rules sometimes enrich IP columns with PTR for analyst readability. Firewalls may log reverse names alongside source addresses. PTR is not authentication — spoofed connections still occur — but human review is faster with names than raw numbers.

When PTR is missing, treat the IP as lower trust in internal scoring models until other intelligence confirms legitimacy.

Identify who controls the reverse zone — usually the ISP, colocation provider, or cloud account that allocated the IP. Provide the desired hostname; they publish PTR in their reverse DNS panel.

After publication, wait for TTL expiry and re-run this lookup. Then verify forward A record alignment. Changes can take hours when upstream caches hold old answers.

Only public IPv4 is supported. Invalid formats and private addresses return validation errors rather than empty lists.

Results reflect DNS at query time via our resolver path. Internal split DNS may differ. This is read-only diagnostics, not a guarantee of mail acceptance.

Combine PTR lookup with our email deliverability checker when auditing SMTP infrastructure. PTR satisfies one column in holistic mail readiness even though SPF and DKIM cover different layers.

For bulk IP investigation, use reverse DNS alongside IP reputation and blacklist tools in the same suite for consistent formatting.