Reverse DNS / PTR Intelligence

Reverse DNS maps an IP address to one or more PTR hostnames. PTR data is useful for infrastructure context, mail-server naming, provider patterns and basic enrichment.

OSINT.dev adds a second step: each returned PTR hostname is resolved forward through A/AAAA queries and marked forward-confirmed when the original IP appears in the forward result.

Why forward confirmation matters

A PTR record by itself is only a DNS label. Forward-confirmation gives stronger evidence that the name and address are mutually configured at lookup time, but it still does not prove:

• legal ownership;
• physical location;
• hosting customer identity;
• beneficial control;
• that all services on the address belong to the same actor.

Only public IPv4/IPv6 input is accepted. Private, link-local, loopback, CGNAT and other non-public ranges are rejected before execution.

References

• Node.js DNS API: https://nodejs.org/api/dns.html
• RFC 1035 — Domain Names Implementation and Specification: https://www.rfc-editor.org/info/rfc1035