URL to IP
Look up every public IPv4 and IPv6 address behind a URL or domain in one call — no need to pick A or AAAA first, both are resolved and listed together.
Input
Any http:// prefix, path or port is stripped automatically before the lookup.
Output
| Property | Value |
|---|---|
| No data yet | |
| Type | Address |
|---|---|
| No data yet | |
More ways to use this tool
REST API
curl -X POST https://api.iotools.cloud/v1/tool/url-to-ip \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "example.com"
}'Swap in your own key from your account. The tool's fields are the body — no wrapper.
Ask an AI agent
Use the IOTools `url-to-ip` tool (URL to IP) on this input:
YOUR_INPUT_HEREPaste this at any agent connected to the IOTools MCP server, then add your input.
| Cost per API/MCP call | From 5 credits |
|---|
Also available with
Guides
What this tool does
Enter a URL or domain and this tool resolves every public IPv4 (A) and IPv6 (AAAA) address behind it in a single lookup, over DNS-over-HTTPS. Unlike a general DNS lookup where you pick one record type at a time, this tool always fetches both address families together and lists them side by side.
How to use it
- Enter a URL or domain name (any
http:///https://prefix, path, or port is stripped automatically). - Click Look up IPs.
- Read the IPv4 and IPv6 addresses found. Copy or download the list as a CSV file.
Frequently asked questions
Why does this run on the server instead of my browser? Browsers can't make DNS-over-HTTPS requests to a resolver on another origin (CORS) and have no built-in DNS API, so the lookup runs server-side. Only Cloudflare's and Google's public DoH resolvers are queried — no other data is sent anywhere.
What if I need other record types — MX, TXT, NS? Use DNS Lookup, which covers A, AAAA, MX, NS, TXT, CNAME, and SOA records one type at a time, with TTLs.
Why do some domains show only one address family? Not every domain has both an A and an AAAA record — IPv6 adoption is still partial. A domain with no result for a family simply isn't advertising an address of that type.
Is this the server that will actually respond when I visit the URL? Usually, but not guaranteed — a domain can sit behind a CDN, load balancer, or DNS-based traffic-steering setup that returns different addresses to different resolvers or locations.