What PTR tells you
A returned hostname is the reverse-DNS name configured for that IP. Many valid IP addresses intentionally have no PTR record.
Resolve a validated IPv4 or IPv6 address to the PTR hostname published by its address owner. DNS only — no port scan or target fetch.
Reverse DNS asks for the PTR name published for one validated IP address.
A returned hostname is the reverse-DNS name configured for that IP. Many valid IP addresses intentionally have no PTR record.
PTR does not require the hostname to resolve back to the same IP, though matched forward-confirmed reverse DNS is common in some mail and infrastructure workflows.
0bps does not connect to the target IP and a PTR result does not prove ownership, service availability, trustworthiness or reachability.
Use authoritative ownership, service and routing sources when those questions matter; do not infer them from PTR text alone.
0BPS SHOWS MEASURED OR CALCULATED FACTS SEPARATELY FROM INTERPRETATION. WHERE A RESULT IS ADVISORY, ESTIMATED OR DESTINATION-SPECIFIC, THE LIMIT IS STATED IN THE TOOL.
It asks DNS for the PTR record associated with a validated IPv4 or IPv6 address. A PTR hostname may not exist even when the address is active.
No. It performs a DNS PTR query only. It does not fetch a web page, scan ports or attempt to identify services on the address.
PTR records are controlled by the address owner or hosting provider and do not have to match every A or AAAA record that points at the address.
The module validates an IPv4 or IPv6 address and asks the server resolver for its PTR record. It does not connect to the target address.
PTR data is normally controlled by the address owner or hosting provider and may be absent or intentionally generic.
Short examples using the same units and assumptions as this module.
A public server IP may resolve to a provider hostname such as a host or edge node name.
A valid public IP can legitimately return no PTR record; this is not a failed IP connection test.