What this check shows
An A record maps a hostname to an IPv4 address. Web browsers, API clients and many other applications use this answer to locate the server that should receive their connection.
DNSRadar compares A record responses across public resolvers so you can identify stale caches, partial propagation and unexpected addresses after a hosting or infrastructure change.
When to use it
- Website or API migrations
- Load balancer and CDN changes
- Unexpected traffic reaching an old server
- Verifying a new hostname before launch
How to read the result
- Multiple addresses can be valid when a service uses load balancing, failover or a CDN.
- A resolver returning an older address may still hold a cached response until its TTL expires.
- NXDOMAIN across every resolver usually indicates a missing name, invalid delegation or an authoritative DNS problem.
Questions
Why are several IPv4 addresses returned?
Many services deliberately publish more than one A record for availability or traffic distribution.
Should every resolver have the same TTL?
No. TTL values decrease while an answer remains cached, so resolvers queried at different moments can show different remaining TTLs.
Related DNS tools
Compare DNS answers worldwide after a record, provider or nameserver change.
Check IPv6 addresses and AAAA record propagation across public DNS resolvers.
Verify canonical name aliases and CNAME propagation across DNS resolvers.
Validate mail server propagation, hostnames and MX priorities worldwide.
Inspect SPF, DKIM, DMARC, ownership verification and other TXT records.
Compare authoritative nameserver records returned by public DNS resolvers.