Every A record for the domain — one or many. Multiple entries typically mean round-robin load balancing or a CDN publishing edge IPs.
A Record Lookup — find the IPv4 address any domain resolves to.
Query the A (address) record for any domain against authoritative DNS servers in real time. Returns every IPv4 address the domain publishes, the TTL for each, and the authoritative source. No caching layer of our own, so you always see what a fresh resolver would see right now. Use it to verify a DNS change, troubleshoot connectivity, or compare against what different geo-regions receive from an Anycast CDN.
Look up an A record right now
Every A lookup queries authoritative nameservers directly — no caching. Returns the IPv4 address list, TTL per record, and the authoritative source.
What the A record lookup shows
Six independently useful outputs from a single query.
Seconds each resolver may cache the answer. 300 = 5 min, 86400 = 24 hours. Critical for planning cutovers.
Which nameserver returned the answer. Non-authoritative resolvers can return stale data during propagation — always cross-check.
Anycast CDNs return different IPs by region. See when your A record is genuinely inconsistent vs. legitimately geographically split.
Every returned IP is one click into a PTR lookup — see if the hostname round-trips back to the same IP (FCrDNS).
One-click into the AAAA lookup to see whether the same host publishes IPv6 alongside IPv4.
When to use an A record lookup
- Verifying a DNS change You just updated the A record at your DNS host. This tool confirms the change is live at the authoritative source (as opposed to still cached at your local resolver, which can take up to TTL to refresh).
- Troubleshooting connectivity Site not loading? First check: does the A record actually resolve to the IP you expect? Missing or stale A is the single most common cause of 'my site is down' reports.
- GeoDNS validation If you're using GeoDNS (Cloudflare, Route 53 latency/geo routing), spot-check that different geo-regions get the intended edge IPs.
- CDN edge inspection See which CDN a domain is fronted by. Cloudflare and Fastly edge ranges are well-known and detectable from the IP list alone.
- Historical comparison Pair with a snapshot tool or your own monitoring to compare today's A record against last week's — spot silent DNS changes before they become incidents.
Common questions
- Why does my A record return multiple IPs? Either DNS round-robin (basic load-balancing — resolver picks one at random) or the domain is behind a CDN publishing multiple edge IPs. Both are normal — not a misconfiguration.
- What's the difference between A and AAAA? A returns IPv4 (32-bit, dotted-quad). AAAA returns IPv6 (128-bit, colon-hex). Dual-stack domains publish both — clients choose based on their reachability.
- Why is a different tool showing a different IP? You're either comparing against a resolver cache (this tool queries authoritative) or against a different geo-region (Anycast CDNs vary by region). Both answers can be simultaneously correct.
- What should my TTL be? Lower TTL (300s = 5 min) before planned changes so propagation is fast. Raise it back afterwards (3600-86400) to reduce query load. Most CDNs default to ~300.
- Does this respect ANAME / CNAME flattening? Yes — CNAME flattening (Cloudflare) and ANAME/ALIAS at the apex return real A records to the querier. This tool sees what the resolver sees, which is the resolved A.
Related DNS tools
Check whether the same domain also publishes IPv6 addresses.
For any IP returned, look up the hostname the IP claims to belong to.
See how the A record looks from resolvers across every continent.
Fetch every DNS record type at once — A, AAAA, MX, TXT, CNAME, NS, SOA, CAA, and more.