Website to IP lookup

Find the IP addresses of a website

Website to IP lookup turns a domain name into the IPv4 and IPv6 addresses. Enter the a domain or url you care about (like example.com or https://example.com/page.html) and this will show you its IPv4 and IPv6 addresses.

This reflects what the zone's authoritative server returns for address lookups, not what a public recursive resolver may still have cached. If the site uses a CDN or geo routing, the address your browser reaches can differ from what you see here — see published DNS vs what clients use below.

How Wirewiki resolves a website's IP addresses

Most online "domain to IP" tools query Google, Cloudflare, or another public recursive resolver. Wirewiki shows you the authoritative view plus infrastructure context:

  • Direct A and AAAA queries. After nameserver discovery, Wirewiki sends both record types to a resolved nameserver address on port 53 (from glue in the NS response when present). Each visit to the results page triggers a fresh address query — Wirewiki does not store DNS answers for this tool.
  • Context on every address. Each IP links to Wirewiki's IP page with ASN (Autonomous System / network owner), country, anycast hints where available, and reserved-range labels.
  • Clickable infrastructure. Propagation checks, per-record CLI commands, DNS history, and related record views are one click away across the site.

Published DNS vs what clients use

This tool answers: "what IPv4 and IPv6 addresses does authoritative DNS publish for this hostname?" That is what you configured at your DNS provider (or what a CDN publishes in DNS), and it is the right check after you change an A or AAAA record.

It is not always the same as "what IP does my browser connect to?" Large CDNs and clouds use anycast, edge routing, or client-specific steering. Your laptop may reach a different edge than the addresses listed here. Compare with DNS propagation when you need to see what recursive resolvers worldwide still cache after a change.

What is website to IP lookup?

The Domain Name System maps names to addresses using A (IPv4, RFC 1035) and AAAA (IPv6, RFC 3596) records. A name can publish multiple addresses, only one address family, or a CNAME alias to another hostname whose addresses live on the target name.

Website to IP lookup shows you this mapping for a domain name.

Reading your results

After you search, Wirewiki opens the IP addresses view for that domain — two stacked tables, one for A and one for AAAA.

Worked example: www.example.com

  1. You enter www.example.com and submit. Wirewiki discovers the authoritative nameserver for the zone, then queries A and AAAA for that name.
  2. A table. Each row is one IPv4 address, sorted for comparison. The header shows record type, description, and TTL. The CLI popup can build an authoritative dig command; the globe icon opens propagation for A on this domain.
  3. AAAA table. Same layout for IPv6. An empty section means the authoritative server returned no records of that type — common when IPv6 is not configured.
  4. Per row. The address links to Wirewiki's IP page; the middle column shows the network owner (ASN and organisation) or a reserved-range label; the right column shows country or an anycast indicator when enrichment is available.

If we've archived this domain, you can also get a date picker on the results page to browse historical A and AAAA snapshots. Connection failures (timeout, unreachable nameserver) show a full-page error state on the same view. When the server answers but returns no address records, the table shows a short in-section message (for example "has no A records") rather than a separate response-code banner.

Wirewiki vs command-line lookup

dig example.com A (or nslookup on Windows) usually hits your configured recursive resolver and returns a non-authoritative answer. Wirewiki complements that by querying the authoritative server for address records and attaching infrastructure context.

Aspect Default CLI (dig / nslookup) Wirewiki website to IP
Server queried Your system or ISP recursive resolver Authoritative server for A / AAAA (after NS discovery via local resolver)
Cache Resolver may serve a cached answer until TTL expires Fresh authoritative A / AAAA each visit; delegation discovery may use resolver cache
IPv4 and IPv6 Two separate commands (A and AAAA) Both record types on one page
CNAME aliases Recursive resolver usually chases; an authoritative dig query on the alias name often fails for out-of-zone targets Follows CNAME RRs from the NS lookup response, then queries addresses for the target name
Enrichment Raw addresses only ASN, country, anycast hints; links to IP and DNS pages
Propagation view Not built in Globe shortcut on each table header

The results header CLI popup uses the hostname you entered; after CNAME aliases the underlying query name may differ. Use DNS trace to verify delegation when lookups fail.

Common situations and what they mean

What you see Likely cause What to verify
Several IPv4 or IPv6 addresses Round-robin DNS, anycast, or multiple origins in the zone Whether all rows are intentional; anycast rows are often CDN edges, not a single machine
Anycast label on an address The same IP is announced from many locations (typical for large CDNs and clouds) Do not assume the address is one physical server near the country shown
Cloud or CDN provider IPs only Hostname is a CNAME to the vendor, or the zone publishes the vendor's anycast range Provider dashboard for origin vs edge; look up the target hostname if address rows are empty
Addresses differ from ping or your browser Recursive cache, geo-steering, or a different hostname (www vs apex) Query the exact hostname; use DNS propagation after a change
No AAAA records IPv6 not configured at the authoritative server Normal for many sites; only matters if you require IPv6 reachability
In-section “has no A records” No A RRset at the authoritative server for the queried name (includes NXDOMAIN-style empty answers) Spelling; apex vs www; whether the name should be a CNAME; try the alias target
Full-page error state (timeout / unreachable) Nameserver unreachable, lame delegation, or network failure to port 53 DNS trace to verify delegation and NS reachability

Command-line lookup

Run these commands to check what your device sees when it looks up a domain name.

macOS, Linux (dig)
dig example.com A +short && dig example.com AAAA +short
Copied
Windows (nslookup — IPv4)
nslookup -type=A example.com
Copied
Windows (nslookup — IPv6)
nslookup -type=AAAA example.com
Copied
Windows (PowerShell)
Resolve-DnsName example.com -Type A; Resolve-DnsName example.com -Type AAAA
Copied

Your device may cache these results for a while. So if you've just changed an address record, you may see the old value here. If you'd like to see the current values, you need to find and query the authoritative nameserver for the domain. You can do this with the commands below.

NS discovery

macOS, Linux (dig)
dig +trace example.com
Copied
Windows (nslookup)
nslookup -debug example.com
Copied

DNS trace on Wirewiki shows the same delegation path with glue in the UI.

A / AAAA on the NS

Substitute ns1.example.com with a nameserver hostname from the trace above.

macOS, Linux (dig — IPv4)
dig @ns1.example.com example.com A +short
Copied
macOS, Linux (dig — IPv6)
dig @ns1.example.com example.com AAAA +short
Copied
Windows (nslookup — IPv4)
nslookup -type=A example.com ns1.example.com
Copied
Windows (nslookup — IPv6)
nslookup -type=AAAA example.com ns1.example.com
Copied

Wirewiki runs NS discovery and dig @… on each search. The results CLI popup copies the authoritative command for the queried name.

  • DNS propagation — what recursive resolvers return after you change an address record.
  • DNS lookup — all common record types from the authoritative nameservers in one view.
  • Reverse IP lookup — IP address to PTR hostname.
  • DNS trace — walk delegation when address lookups fail.
  • A lookup and AAAA lookup — tools for just the IPv4 and IPv6 addresses, respectively.

Frequently asked questions

Is this the IP address my browser connects to?

Often, but not always. Wirewiki shows the addresses the authoritative server returned for this lookup. CDNs, anycast, and geo routing can send users to different edges than the rows listed. Use propagation checks or your provider's dashboard when you need the client path, not just published DNS.

Should I enter the apex (root domain) or www?

They are different DNS names and may have different records. Enter the exact hostname you care about — example.com and www.example.com often diverge when one is a CNAME to the other or to a CDN. Apex CNAME is often implemented as ALIAS/ANAME flattening at the provider; this tool shows the resolved addresses, not the alias record itself.

How is this different from DNS propagation?

Website to IP asks the authoritative nameserver for address records. Propagation compares answers from many recursive resolvers worldwide to see whether a change has spread. Verify what you published here; use propagation to see what resolvers still cache.

Can I see past IP addresses for a domain?

For domains in Wirewiki's archive, the results page includes a date picker for historical A and AAAA snapshots. Not every domain on the internet is archived.