IPv4/IPv6 Compatibility
See whether a domain publishes IPv4 and IPv6 records.
Use the IPv4/IPv6 Compatibility tool
What this ipv4/ipv6 compatibility does
IPv4/IPv6 Compatibility checks whether a host publishes both address families. Enter an IP literal and the tool classifies it, or enter a domain and it queries A and AAAA records in parallel, then summarises the result as IPv4 only, IPv6 only or dual stack.
Publishing an AAAA record does not prove the IPv6 path works. It only shows that the name resolves over IPv6. You still need to confirm that the server listens on IPv6 and that firewalls allow it, which this tool cannot test.
Why use it
- Find domains that still have no IPv6 address.
- Confirm a migration added AAAA records without removing A records.
- Recognise private, loopback and reserved literals before troubleshooting.
How to use it
- 1Enter a domain or an IP address.
- 2Run the check.
- 3Read the address-family verdict and the records returned.
- 4For IPv6-only results, confirm that IPv4 users can still reach the service through a proxy or gateway.
Worked examples
Dual stack
Input
A domain with both A and AAAA records
Output
The verdict is dual stack, with one or more addresses of each family listed.
IPv4 only
Input
A domain with A records and no AAAA
Output
The verdict is IPv4 only, and the tool notes that IPv6 clients must fall back.
Common mistakes
- Assuming an AAAA record means the site answers over IPv6.
- Adding AAAA records for servers that do not listen on IPv6, which breaks connectivity for IPv6-first clients.
- Forgetting that CDN hostnames often have different families than origin servers.
Frequently asked questions
What counts as dual stack?
The name returns at least one A record and at least one AAAA record.
Why does a domain return no records?
It may not exist, be misconfigured, or use a resolver that filtered the answer.
Can I check a private address?
Yes, as a literal. The tool classifies it and warns that it is not routable on the public internet.
Does it test connectivity?
No. It checks DNS records only, not whether packets actually reach the host.