A and AAAA record lookup
Resolve IPv4 A records, IPv6 AAAA records or both. Each result keeps the hostname, record type, IP address and resolver message visible, which makes mixed IPv4/IPv6 checks easier to compare.
Network Tools
| Hostname | Type | IP Address | TTL | Resolver | Message | Copy |
|---|---|---|---|---|---|---|
| No DNS lookup has run yet. | ||||||
Run a lookup to see JSON output.
DNS diagnostics
This Hostname to IP page resolves a domain or URL into A and AAAA DNS records through an explicit DNS-over-HTTPS lookup. It helps developers, DevOps teams, support staff and QA testers confirm what IP addresses a hostname currently returns before debugging APIs, CDNs, load balancers or deployment changes. Paste one hostname or URL per line, choose Cloudflare or Google as the resolver, select IPv4 A records, IPv6 AAAA records or both, then review IP addresses, TTLs, resolver source and messages. Results can be copied or exported as CSV or JSON.
Resolve IPv4 A records, IPv6 AAAA records or both. Each result keeps the hostname, record type, IP address and resolver message visible, which makes mixed IPv4/IPv6 checks easier to compare.
The input accepts one hostname or URL per line, normalizes full URLs to hostnames, removes trailing dots and reports invalid labels, single-label names, IPv6 literals or already-entered IPv4 addresses.
Choose Cloudflare or Google DNS-over-HTTPS, then inspect TTL values, resolver source and messages. Copy individual IPs, copy the full result set or download CSV and JSON reports.
Resolve an API hostname before using the API Test tool, especially when requests are failing after a deployment or DNS change.
Check which edge, proxy or load-balancer addresses a hostname returns. DNS can show the public records, but it does not expose every backend server behind that layer.
Compare A and AAAA answers when a service works on one network but not another, or when rolling out IPv6 support.
Export the resolver, TTL and result messages so a ticket includes the exact DNS answer seen during the test.
Use fully qualified names such as api.example.com. Full URLs are accepted and converted to their hostname before DNS lookup.
The table shows hostname, type, IP address, TTL, resolver and message. TTL is reported in seconds by the DNS answer and helps explain cache behavior.
Already-entered IPv4 addresses, IPv6 literals, single labels and invalid hostname labels are rejected. Use IP to Hostname for reverse DNS.
This tool resolves DNS records only. It does not test website uptime, active ports, TLS, ownership, IP geolocation or application health. DNS answers can vary by resolver cache, TTL, geography, CDN routing and record configuration, so the table reflects the selected resolver at the time you run the lookup. Hostnames are sent to the selected public DNS-over-HTTPS resolver to perform the query. For MX, NS, TXT, CNAME, SOA, SRV or CAA records, use the broader DNS Lookup tool.
It queries DNS A and AAAA records for valid hostnames using the selected DNS-over-HTTPS resolver and returns IP addresses, TTLs, resolver source and messages.
Yes. Full URLs are normalized to their hostname before lookup. Paths, query strings and fragments are ignored because DNS records belong to the hostname.
DNS answers can vary by resolver cache, TTL, geography, CDN routing and record configuration. This page shows the result from the resolver you selected.
No. A and AAAA records may point to CDN edges, proxies or load balancers. They do not reveal every origin or backend server behind that layer.
No. It resolves DNS records only. It does not test website uptime, HTTP health, TLS, active ports, geolocation or ownership.
Yes. After lookup, you can copy results or download CSV and JSON reports for support notes, deployment checks or audit records.