What Domain To IP does
Domain To IP performs a server-side DNS resolution for the normalized host and returns up to sixteen public address records, including address family information. It is useful for seeing which endpoints the PagesTools resolver receives at the moment of the request.
A DNS answer is not a permanent server identity. CDNs, anycast networks, regional routing, load balancers, short TTLs, and resolver caches can produce several or changing results. Use the addresses as a diagnostic snapshot and consult authoritative DNS or provider records when an exact infrastructure decision depends on them.
How to use Domain To IP
- Enter a public domain such as example.com without a path or query string.
- Select Resolve domain to request current A and AAAA resolution.
- Review each returned address and its IPv4 or IPv6 family.
- Repeat from the relevant network or use authoritative DNS data if regional differences matter.
Important details
Public addresses only
The resolver rejects answers that point to private, loopback, link-local, or otherwise reserved destinations. This means it is not an internal DNS troubleshooting tool.
A and AAAA can both appear
IPv4 addresses come from A records and IPv6 addresses from AAAA records. A site may publish one family, both families, or several addresses for the same family.
Results are capped
The response includes no more than sixteen public addresses. That cap prevents unusually large DNS answers from overwhelming the interface and should not be read as a complete historical inventory.
Practical uses
- Confirm that a recent DNS change resolves to the expected public network.
- Collect endpoint addresses before testing routing or firewall behavior.
- Compare whether a host publishes IPv4, IPv6, or both.
Privacy and limitations
The domain is sent to PagesTools for a DNS lookup, so the server's configured resolver can observe the query. No page content is fetched, and the JSON response is returned with no-store cache headers.
The lookup reflects one resolver at one time, may differ by location or cache, and is capped at sixteen addresses. It does not identify an origin server behind a CDN or prove who controls an address.