What This Website IP Lookup & Reverse DNS Inspector Does
This network diagnostic tool resolves any website URL, domain name (including internationalized Punycode IDNs), or public IP address to its authoritative IPv4 (A) and IPv6 (AAAA) records, Reverse DNS pointer (PTR) hostname, CNAME aliases, NS nameservers, and MX mail exchangers. The top summary bar displays the primary public IPv4, primary IPv6, Reverse DNS pointer and .in-addr.arpa zone, detected edge network / ASN provider (such as Cloudflare Anycast AS13335, Google Edge AS15169, AWS CloudFront AS16509, Fastly, Akamai, or GitHub), minimum DNS TTL, and query latency in milliseconds.
For low-level network and database work, the tool converts the primary IPv4 address into its 32-bit unsigned integer (ip2long / INET_ATON), hexadecimal format (0x...), /24 CIDR subnet prefix, and 32-bit dotted binary octets, and expands the primary IPv6 address to its full uncompressed 128-bit canonical form (RFC 4291). You can test instant preset benchmarks (cloudflare.com, google.com, github.com, wikipedia.org, 8.8.8.8) and copy any resolved record with one click.
How Domain-to-IP Resolution Powers Every Internet Connection
Every device connected to the global internet routes packets using numerical Internet Protocol (IP) addresses rather than human-readable domain names. When you type a URL into your browser, the operating system stub resolver and recursive DNS resolvers must translate that hostname into a routable Layer-3 network address before a single TCP SYN packet or QUIC datagram can leave your network interface card (NIC).
Our Website IP Lookup & Reverse DNS Inspector queries the global Domain Name System hierarchy in real time to uncover the complete dual-stack routing profile behind any website:
- IPv4 Address Records (
A— RFC 1035): Maps a hostname to a 32-bit IPv4 address written in dotted-decimal notation (such as104.16.132.229). The entire IPv4 address space contains 232 = 4,294,967,296 possible addresses. - IPv6 Address Records (
AAAA— RFC 3596): Maps a hostname to a 128-bit IPv6 address written in hexadecimal groups (such as2606:4700::6810:84e5). Because 2128 ≈ 3.4 × 1038, IPv6 eliminates NAT exhaustion and enables direct end-to-end routing across modern 5G mobile and fiber networks. - Canonical Name Aliases (
CNAME) & Name Servers (NS): Reveals whether a subdomain aliases to a third-party SaaS platform or CDN endpoint (such as*.cloudfront.netor*.github.io) and identifies the authoritative DNS providers managing the zone.
Dual-Stack Routing, Happy Eyeballs (RFC 8305), and BGP Anycast CDNs
When inspecting enterprise domains like cloudflare.com, google.com, or wikipedia.org, you will notice that DNS rarely returns a single static IP address. Instead, modern web architecture relies on two foundational routing mechanisms:
- Happy Eyeballs Version 2 (IETF RFC 8305): When a domain publishes both IPv6 (
AAAA) and IPv4 (A) records, modern browsers query both simultaneously. The client initiates an IPv6 connection first with a tiny 50 ms to 250 ms connection timer; if the IPv6 path fails or stalls, the browser immediately races a parallel IPv4 TCP/QUIC connection and uses whichever handshake completes first. - BGP Anycast Edge Networks: Major CDNs and DNS providers announce the exact same IP prefix (for example,
104.16.0.0/12or1.1.1.0/24) from over 300 physical Points of Presence (PoPs) worldwide using the Border Gateway Protocol (BGP). When a user in Frankfurt, Tokyo, or New York resolves a Cloudflare-protected website, all three users may see the exact same IPv4 address—yet their packets are routed to the physically nearest regional data center.
32-Bit IPv4 Integer Math, Hexadecimal Subnets, and 128-Bit IPv6 Canonicalization
Storing IP addresses as variable-length ASCII strings (VARCHAR(15) or VARCHAR(45)) inside high-volume SQL databases, firewall lookup tables, or analytics engines is inefficient and breaks numeric range queries (BETWEEN). Network engineers and backend developers convert dotted-quad IPv4 addresses into 32-bit unsigned integers using big-endian bit shifting:
For example, given the IPv4 address 104.16.132.229:
- Decimal Octet Expansion: (104 × 16,777,216) + (16 × 65,536) + (132 × 256) + 229 = 1,744,830,464 + 1,048,576 + 33,792 + 229 = 1,745,876,197.
- Hexadecimal Representation: Converting each octet to base-16 (104 = 0x68, 16 = 0x10, 132 = 0x84, 229 = 0xE5) yields
0x681084E5. - Dotted Binary Octets:
01101000.00010000.10000100.11100101, making it trivial to apply a/24subnet mask (255.255.255.0) to isolate the network prefix104.16.132.0/24.
Reverse DNS (PTR) and the .in-addr.arpa / .ip6.arpa Hierarchy
Because the Domain Name System is indexed hierarchically from most-general (rightmost TLD) to most-specific (leftmost host label), whereas IP addresses are written from most-general network prefix (leftmost octet) to most-specific host interface (rightmost octet), performing a Reverse DNS (rDNS) lookup requires reversing the order of the IP octets or hexadecimal nibbles:
- IPv4 Reverse Zone (
in-addr.arpa): To look up thePTRrecord for8.8.8.8or104.16.132.229, the resolver reverses the four octets and appends.in-addr.arpa, querying229.132.16.104.in-addr.arpa. - IPv6 Reverse Zone (
ip6.arpa): Every single hexadecimal digit (4-bit nibble) of the full 32-character uncompressed IPv6 address is reversed and separated by dots under.ip6.arpa. Verifying both forward and reverse DNS records is essential when auditing server ownership, diagnosing SMTP email deliverability blocks, and verifying genuine search engine crawlers like Googlebot (which always resolve back to*.googlebot.comor*.google.com).