DNS lookup methodology
Domain IP Lookup reports publicly resolved DNS data at the time of the request. It does not infer an origin server or claim that a returned address belongs to a specific physical machine.
Normalize the input
The service accepts a hostname or URL, removes schemes, paths, ports, and trailing dots, and validates the resulting public hostname.
Query DNS records
A and AAAA records provide IPv4 and IPv6 results. NS, MX, CNAME, and TXT records are queried independently when available.
Validate addresses
Returned addresses are checked against private, loopback, link-local, and cloud-metadata ranges before they are included in the result.
Handle failures clearly
NXDOMAIN and invalid input fail without pointless retries. Timeouts, SERVFAIL, and REFUSED can be retried with bounded backoff.
Process bulk jobs safely
Bulk requests are persisted as jobs and processed by a controlled worker so large lists do not block the web request.
Records included in a lookup
AIPv4 addresses published for the hostname.
AAAAIPv6 addresses published for the hostname.
NSNameservers delegated for the domain.
MXMail exchangers and their DNS priorities.
CNAMEAliases returned for the queried hostname.
TXTText records, commonly used for verification and email policies.
Resolver behavior and limitations
The server uses configurable public DNS resolvers, with an additional system-resolver fallback for networks that block a particular provider. Each record query has a bounded timeout. A successful result means at least one usable public A or AAAA address was returned; an optional record type may be absent.
This service does not perform reverse DNS, port scanning, HTTP redirects, geolocation, ASN discovery, or origin-server discovery. A CDN, proxy, load balancer, or geographic DNS policy can change the answer.
DNS answers may differ over time or between resolver locations because of TTLs, CDNs, geographic routing, failover, and provider configuration.