How to use
01
Type the domain
Enter a registered name such as example.com in the Domain field. Pressing Enter works the same as clicking the button, handy when you're checking several names in a row.
02
Click Resolve
The server runs dns.resolve4 and dns.resolve6 for the name and returns every published address, split cleanly into an IPv4 column and an IPv6 column.
03
Compare both columns
Look at the count beside each column header. A dual-stack setup lists at least one address in each, and every entry has a one-click copy button.
Why Domain to IP
- Resolve a domain to both IPv4 and IPv6 addresses.
- Multiple addresses shown if the domain has them.
- Uses Node's dns.resolve4 / dns.resolve6 directly.
Common questions
Why does my domain resolve to several IP addresses?
Multiple A records are a standard availability trick. Load balancers, round-robin DNS, and CDN edge networks all publish several addresses so traffic spreads out and a single dead server doesn't take the site down. Seeing two or more entries is usually a good sign.
What does None in the IPv6 column mean for my domain?
The domain publishes no AAAA record, so it's reachable over IPv4 only. That's still common and nothing is broken, but adding IPv6 is worth planning since a growing share of mobile networks prefer it.
Can a domain ip lookup tell me which company hosts a site?
It gets you halfway. The resolved address belongs to a hosting provider's range, so feeding that IP into a WHOIS query against the regional registry usually names the company. Just remember that a CDN address points at the CDN, not the origin host.
Is the IP behind a domain always the real web server?
No. If the site sits behind Cloudflare or another proxy, you're resolving the proxy's edge address, and the origin server stays hidden by design. That's exactly what you want to know when debugging why firewall rules aimed at the origin never fire.
How often does the IP of a domain change?
It varies wildly. A small site on a fixed VPS can keep one address for years, while CDN-fronted domains rotate answers between requests. If you're allowlisting, resolve the domain a few times across a day before trusting a single answer.
Does resolving a domain to IP here differ from ping or nslookup?
They read the same DNS records, so results normally match. When they don't, the culprit is almost always caching: your local machine or router is holding an older answer, while this lookup runs fresh from the server side.