Back to Tools IP & DNS PRO

Website IP Lookup & Reverse DNS (PTR) Inspector

Find the public IPv4 (A) and IPv6 (AAAA) addresses behind any domain or URL in real time, complete with Reverse DNS (PTR), 32-bit integer/hex/binary representations, ARPA zone, and Anycast CDN fingerprinting.

Instant Benchmarks:
Primary Public IPv4
104.16.132.229
Host: cloudflare.com (TTL 300s)
Primary IPv6 (AAAA)
2606:4700::6810:84e5
Dual-Stack IPv4 + IPv6 Active
Reverse DNS (PTR)
104.16.132.229 (Anycast)
229.132.16.104.in-addr.arpa
Edge Network / ASN
Cloudflare Anycast Edge (AS13335)
Resolved in 12.4 ms

📡 Resolved IPv4 (A), IPv6 (AAAA) & NS Records

All authoritative round-robin / Anycast IP addresses and nameservers:

A · 104.16.132.229
A · 104.16.133.229
AAAA · 2606:4700::6810:84e5
AAAA · 2606:4700::6810:85e5
NS · ns3.cloudflare.com, ns4.cloudflare.com

🔢 IPv4 32-Bit Numeric & IPv6 128-Bit Representations

Low-level socket, firewall CIDR, and database representations of the primary IP:

IPv4 32-Bit Unsigned Integer (ip2long)
1745876197
IPv4 Hexadecimal & /24 Subnet Prefix
0x681084E5 · Subnet 104.16.132.0/24
IPv4 32-Bit Dotted Binary Octets
01101000.00010000.10000100.11100101
IPv6 Uncompressed 128-Bit Canonical Form (RFC 4291)
2606:4700:0000:0000:0000:0000:6810:84e5
Reverse DNS Pointer Zone (RFC 1035 in-addr.arpa)
229.132.16.104.in-addr.arpa

Global Anycast DNS, CDN & Infrastructure IP Reference Table

Pre-calculated IPv4, IPv6, 32-bit unsigned integer, hexadecimal, and Autonomous System (ASN) benchmarks:

Hostname / Service Primary IPv4 (A) Primary IPv6 (AAAA) 32-Bit Integer Hexadecimal Autonomous System (ASN)
cloudflare.com 104.16.132.229 2606:4700::6810:84e5 1745876197 0x681084E5 AS13335 (Cloudflare Anycast)
dns.google 8.8.8.8 2001:4860:4860::8888 134744072 0x08080808 AS15169 (Google Public DNS)
one.one.one.one 1.1.1.1 2606:4700:4700::1111 16843009 0x01010101 AS13335 (APNIC / Cloudflare)
dns.quad9.net 9.9.9.9 2620:fe::fe 151587081 0x09090909 AS19281 (Quad9 Anycast Security)
github.com 140.82.121.4 — (IPv4 Only Origin) 2354215172 0x8C527904 AS36459 (GitHub Inc.)
wikipedia.org 185.15.59.224 2a02:ec80:300:ed1a::1 3104783328 0xB90F3BE0 AS14907 (Wikimedia Foundation)

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 as 104.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 as 2606: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.net or *.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/12 or 1.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:

Integer32 = (Octet1 × 224) + (Octet2 × 216) + (Octet3 × 28) + Octet4

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 /24 subnet mask (255.255.255.0) to isolate the network prefix 104.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 the PTR record for 8.8.8.8 or 104.16.132.229, the resolver reverses the four octets and appends .in-addr.arpa, querying 229.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.com or *.google.com).

Frequently Asked Questions About Website IP Addresses & Reverse DNS

Why does a website return multiple IPv4 and IPv6 addresses?

Modern high-availability websites publish multiple DNS A (IPv4) and AAAA (IPv6) records for two primary reasons: DNS Round-Robin load balancing (distributing incoming client connections across multiple origin or proxy servers) and Border Gateway Protocol (BGP) Anycast fault tolerance (providing backup edge IPs so browsers can fail over in under 250 milliseconds via Happy Eyeballs RFC 8305 if one route is congested).

Why does my website show a Cloudflare, Fastly, or CloudFront IP instead of my hosting server IP?

When a domain uses a reverse-proxy Content Delivery Network (CDN) or Web Application Firewall (WAF) like Cloudflare, AWS CloudFront, or Fastly, authoritative DNS deliberately returns the public Anycast edge IP of the CDN rather than your origin server IP. This hides your origin server from direct DDoS attacks and serves cached assets from the physical data center closest to the visitor.

What is a Reverse DNS (PTR) record and why is it important?

While a standard forward DNS lookup translates a domain name into an IP address, a Reverse DNS (rDNS) lookup queries a special pointer record (PTR) under the .in-addr.arpa (IPv4) or .ip6.arpa (IPv6) zone to map an IP address back to its canonical server hostname. Outbound mail servers (SMTP) and enterprise firewalls strictly verify that an IP has a matching forward-confirmed reverse DNS (FCrDNS) record before accepting traffic.

How do you convert a dotted-quad IPv4 address into a 32-bit integer?

An IPv4 address consists of four 8-bit octets (A.B.C.D), totaling 32 bits in big-endian network byte order. To convert it to an unsigned 32-bit integer (used in MySQL INET_ATON() or PHP ip2long()), compute: (A × 16,777,216) + (B × 65,536) + (C × 256) + D. For example, 8.8.8.8 equals (8 × 16,777,216) + (8 × 65,536) + (8 × 256) + 8 = 134,744,072 (0x08080808).

How does IPv6 address compression work under RFC 4291 and RFC 5952?

An IPv6 address is 128 bits long, written as eight 16-bit hexadecimal groups separated by colons (for example, 2606:4700:0000:0000:0000:0000:6810:84e5). Under RFC 5952 canonical compression rules, leading zeros within any 16-bit group are omitted, and the longest contiguous run of all-zero groups is replaced once by a double colon (::), yielding 2606:4700::6810:84e5.

How does this tool handle internationalized domain names (IDNs) and full URLs?

You can paste a complete URL (including https://, paths, and query parameters) or a Unicode domain name containing non-ASCII characters (such as café.example or ąžuolas.lt). Our parser automatically strips URI schemes and paths, converts Unicode labels into RFC 3492 Punycode (xn--...) via idn_to_ascii, and resolves the authoritative DNS records.