Domain IP Lookup is a focused, no-nonsense tool for resolving domain names to their public IPv4 and IPv6 addresses -- one at a time, in bulk, or on a schedule.
Every resolution happens directly through Node.js's built-in dns module, querying public DNS servers in real time. There is no third-party IP lookup API in the middle -- what you see is exactly what this server's own DNS resolver got back.
Most “domain to IP” tools online quietly proxy your lookup through a third-party API, log the domains you search, or bury the actual answer behind ads and unrelated affiliate content. We wanted something that just does the one job -- resolve a domain, show the IPs, nothing else in the way -- and that scales from a single curious lookup to a scheduled job watching thousands of domains.
Developers checking where a domain actually points before debugging a connectivity issue. Infrastructure and SRE teams tracking DNS changes across a large domain portfolio on a recurring schedule. Security researchers who need a safe way to resolve large domain lists without the tool itself becoming an internal-network scanning risk. Anyone who just wants a fast answer without an account wall.
The frontend is Next.js, React, and TypeScript. Every lookup -- single or bulk -- runs through Node's own dns.Resolver, with configurable upstream DNS servers and timeouts. Bulk and scheduled jobs are persisted to Postgres and processed by a separate background worker through a Redis-backed job queue (BullMQ), so a 10,000-domain batch never ties up a web request or gets lost if the server restarts mid-job.
Every resolved address is checked against private, loopback, link-local, and cloud-metadata ranges before it's ever returned, closing the DNS-rebinding gap that many simpler lookup tools miss. Rate limiting and bulk-job caps keep the service available and abuse-free for everyone.
A DNS result is the public address returned for the domain at lookup time. It may belong to a CDN, reverse proxy, load balancer, or hosting provider, so it is not a guarantee of the origin server's physical address. DNS answers can also vary by resolver location, record type, TTL, and traffic configuration.
Read how the lookup works, review the security controls, or contact us with feedback.
No account, no tracking beyond what's needed to enforce rate limits, and no data sold to anyone.