Home SEO Tools Domain to IP

Domain to IP - IPv4, IPv6, TTL, Hosting & Bulk Lookup

Find the IP address of any domain instantly - IPv4 and IPv6, TTL, hosting provider detection, full DNS record types (A, AAAA, CNAME, MX, NS, TXT), bulk lookup up to 10 domains, and search history. Uses Google DNS - real-time, accurate, private.

Always Free IPv4 + IPv6 + TTL Bulk lookup (10 domains) Powered by Google DNS
A · AAAA · CNAME · MX · NS · TXT records
Real-time DNS lookup via Google DNS-over-HTTPS - always accurate
IPv4 and IPv6, TTL, and hosting provider shown together
Bulk lookup - resolve up to 10 domains simultaneously
Try: google.com · github.com · cloudflare.com · amazon.com · wikipedia.org
Querying DNS via Google DNS-over-HTTPS...
Domain resolved
Resolved
IPv4 Address (A record) Primary
-
IPv6 Address (AAAA record) Modern
-
Hosting & server details
Provider / CDN
-
IP class
-
CDN detected
-
How DNS resolution works - the journey from domain to IP
🖥️
Your browser
types google.com
📋
OS cache
checks local cache
🔄
Resolver
ISP or 8.8.8.8
🌐
Root DNS
13 root servers
📁
TLD server
.com, .org, .net
Auth. NS
domain nameserver
🖥️
Server IP
returned to browser
Recent lookups - click to re-lookup

Other IP lookup tools show one number.
This shows the full DNS picture.

IPv4 + IPv6, TTL, hosting provider, bulk lookup, all record types, DNS flow diagram, and history - built for developers and SEO professionals.

IPv4 + IPv6 + TTL together

Both address types and the TTL value shown simultaneously - not just the IPv4 address. TTL tells you how long the record is cached, critical for understanding DNS propagation timing.

complete DNS picture

Bulk lookup - 10 at once

Paste up to 10 domains and resolve all simultaneously. Export results as CSV. Useful for auditing hosting infrastructure or verifying DNS after migration.

save hours of manual checking

All DNS record types

Switch between A, AAAA, CNAME, MX, NS, and TXT records in one place - not just the IP address. See mail servers, nameservers, and verification tokens.

A to TXT in one tool

DNS resolution flow diagram

Interactive visual showing the full journey from browser to IP - browser cache, OS cache, ISP resolver, root servers, TLD servers, authoritative nameserver. Helps users understand what they are querying.

learn while you use

Lookup history

Last 10 domains you looked up saved in session - click any to re-lookup instantly. No need to retype domains you check regularly.

no retyping

Google DNS - real-time

Uses Google DNS-over-HTTPS (8.8.8.8) for every lookup - not a cached database. Results are always current, reflecting the latest DNS propagation state.

always accurate

Find any domain's IP in seconds

1

Enter a domain name

Type any domain (e.g. github.com) - no need to include http:// or www. Press Enter or click Look up IP.

2

See IPv4, IPv6 and TTL

Both IP address versions are shown instantly with TTL and detected hosting provider. Copy either address with one click.

3

Explore all record types

Switch to DNS Records mode to see MX (mail), NS (nameservers), CNAME, and TXT records. Use Bulk mode to check 10 domains at once.

Domain to IP - understanding DNS and why it matters

Every website you visit has a numeric IP address as its true identifier. The domain name system (DNS) is the internet's phone book - it translates human-readable names like google.com into machine-readable addresses like 142.250.80.46. Without DNS, you would need to memorise IP addresses to visit websites.

Why you would need to look up a domain's IP address

Use caseWhat to look for
Verify DNS after migrationIP should match your new hosting server
Check if behind a CDNCloudflare IPs: 104.16.0.0/12, Fastly: 151.101.0.0/16
Shared hosting auditMultiple domains resolving to same IP
Debug connectivity issuesIP to ping directly, bypassing DNS
SEO link auditPBN detection - many domains on same IP
Security investigationIdentify suspicious hosting infrastructure
CDN detection tip. If a domain returns an IP in the range 104.16.0.0–104.31.255.255, it is behind Cloudflare. Fastly CDN uses 151.101.0.0/16. Amazon CloudFront uses 52.84.0.0/15 and 54.230.0.0/15. When a domain is behind a CDN, the returned IP is not the actual server IP - it is a CDN edge node IP. You cannot reach the origin server directly using this IP unless you know the origin IP separately.

IPv4 vs IPv6 - which one matters more?

IPv4 (e.g. 142.250.80.46) is the legacy 32-bit address format with approximately 4.3 billion possible addresses. IPv4 addresses are nearly exhausted. IPv6 (e.g. 2607:f8b0:4004:c07::71) is the modern 128-bit format with 340 undecillion addresses - enough for every device on earth and beyond. Most major websites support both. Your browser automatically uses IPv6 if available, falling back to IPv4. Both are shown in this tool when available.

What is TTL and why does it affect DNS propagation?

TTL (Time to Live) is the number of seconds DNS resolvers cache a record before re-querying the authoritative nameserver. A TTL of 300 means the IP address is cached for 5 minutes. A TTL of 86400 means it is cached for 24 hours. When you change your DNS records, the old IP address continues to be served by caching resolvers until their TTL expires. This is why DNS changes can take up to 48 hours to propagate globally - though modern low-TTL setups can propagate in minutes.

DNS questions,
answered.

Ask a question
A domain to IP lookup translates a human-readable domain name (like google.com) into the numerical IP address of the server that hosts it. This is the same process your browser performs every time you visit a website, using the Domain Name System (DNS).
IPv4 uses a 32-bit format shown as four groups of numbers (e.g. 142.250.80.46). IPv6 uses a 128-bit format shown as eight groups of hexadecimal characters. IPv6 was introduced because IPv4 addresses are nearly exhausted. Most websites support both.
TTL (Time to Live) is how many seconds a DNS record is cached before resolvers must re-query the authoritative server. A TTL of 300 = 5 minutes caching. Lower TTL means DNS changes propagate faster but create more queries.
Yes. Shared hosting puts many websites on a single server with one IP. Virtual hosting allows the server to serve different websites based on the domain name in the HTTP request. This is very common, especially on affordable hosting plans.
Large websites return multiple IPs for load balancing - distributing traffic across many servers. CDN services like Cloudflare also return different IPs based on the visitor's geographic location to serve content from the nearest edge server.
DNS propagation is the time it takes for a DNS record change to spread across all DNS servers worldwide. It can take a few minutes to 48 hours depending on the previous record TTL. During propagation, different users may see different IPs for the same domain.