IPv6 Website Test
Test whether a website supports IPv6: check its AAAA records, see if it is dual-stack, and confirm it is actually reachable over IPv6.
Type a domain name or URL to test its IPv6 compatibility.
Every network tool you'll ever need.
Purpose-built utilities for ports, IPs, DNS and email. Completely free, all powered by external probes.
Port Checker
Probe any TCP port on any host
DNS Lookup
Look up the IP addresses behind a domain
rDNS Check
Reverse DNS: map IPs back to hostnames (PTR)
Ping Tool
Check host reachability with ICMP
Speed Test
Gauge download, upload and latency
Proxy Check
Spot VPN or proxy usage
Link Checker
Confirm whether URLs are reachable
HTTP Headers Checker
Examine response headers
What Is My IP?
Reveal your current public IP
IP Subnet Calculator
Work out masks, ranges and CIDR math
IP Converter
Convert between IPv4 and IPv6 either way
ASN Lookup
Look up org, ISP and IP ranges by ASN
IP Blacklist Checker
See whether an IP is spam-listed
IPv6 Website Test
Test if a website supports IPv6 (AAAA + reachability)
SPF Record Checker
Verify your email sender policy
DMARC Validator
Read policy, alignment and reporting config
DKIM Checker
Validate DKIM signatures
Email Header Analyzer
Follow email origin and routing
IPv6 Website Test: Check Whether Your Domain Is Reachable Over IPv6
This tool checks whether a domain supports IPv6 by querying its DNS records and then attempting an actual network connection over IPv6. It looks up the domain's AAAA records (the IPv6 equivalent of an A record) and tests whether the resolved addresses are reachable, not just listed in DNS. That distinction matters because a published AAAA record does not guarantee a live, accessible server.
Use this page to check IPv6 website connectivity for any domain you manage or depend on, and to confirm whether your deployment is dual-stack (reachable on both IPv4 and IPv6) or limited to one protocol only.
Why IPv6 Support Matters for Your Site
IPv4 address exhaustion has been a real constraint for years. Mobile carriers and some ISPs now route traffic over IPv6 by default. A site with no AAAA records is invisible to IPv6-only clients unless a translation layer is in place.
Dual-stack is the recommended configuration. It means your server has both an A record (IPv4) and an AAAA record (IPv6), so clients on either protocol can reach it directly. Running IPv4-only leaves a growing share of traffic dependent on carrier-grade NAT or other workarounds, which can add latency or drop connections entirely.
- IPv6-only mobile networks are common in markets like the United States, India, and Germany.
- Google, Cloudflare, and other major platforms prioritize dual-stack configurations.
- Search crawlers increasingly support IPv6, and a missing AAAA record can affect crawl behavior.
- Enterprise networks often enforce IPv6 internally, making external IPv4-only sites harder to reach.
How the IPv6 Compatibility Checker Works
When you submit a domain, the tool performs two distinct operations. First, it queries DNS for both A records (IPv4) and AAAA records (IPv6) and records all resolved addresses. Second, it attempts a TCP connection to the resolved IPv6 addresses, trying port 80 first and then port 443 if port 80 does not respond, with a 3-second timeout per attempt.
The result tells you whether the domain has IPv6 addresses, whether it has IPv4 addresses, whether it qualifies as dual-stack, and what the connectivity status is: reachable, unreachable, or unknown. "Unknown" typically means the test server could not determine reachability within the timeout window, often due to a firewall silently dropping packets rather than sending a rejection.
Because the connectivity test runs from the pingie.net server, results reflect reachability from that server's network perspective. A firewall rule blocking the test server's IP range could show "unreachable" even if your site is accessible from most other locations.
How to Use the Tool: Step by Step
- Open the IPv6 Compatibility Checker from the tool menu on this page.
-
Enter a domain name or full URL in the input field (for example,
example.comorhttps://example.com). - Click Check . The tool queries DNS and runs the connectivity test.
- Review the results: AAAA and A records found, all resolved IPv6 and IPv4 addresses, dual-stack status, and connectivity status.
No account or login is needed. The tool does not store domain names you submit beyond the duration of the request.
When to Run an IPv6 Check
There are several situations where checking IPv6 site compatibility is worth doing deliberately rather than waiting for a user report.
- After a DNS change: New hosting, CDN migration, or nameserver update can inadvertently remove AAAA records.
- Before a launch: Confirm dual-stack is in place before traffic ramps up.
- Debugging connectivity complaints: Users on IPv6-only networks may report intermittent failures that are invisible from an IPv4 connection.
- After a firewall change: A new firewall rule can block IPv6 traffic even when the AAAA record remains valid in DNS.
- Routine audits: Periodic checks catch configuration drift before it becomes a user-facing problem.
For a broader view of your domain's DNS health, the DNS Lookup tool lets you query individual record types across your zone.
What the Results Tell You
The output covers four key data points. Understanding each one helps you act on the result rather than just read it.
- has_ipv6 / AAAA records: Confirms whether the domain publishes any IPv6 addresses in DNS at all. No AAAA record means no IPv6 support, period.
- has_ipv4 / A records: Confirms IPv4 presence. A domain with AAAA but no A records is IPv6-only, which can exclude a large share of users.
- is_dual_stack: True only when both A and AAAA records exist. This is the target state for most public-facing websites.
- connectivity_status: The result of the actual TCP connection attempt. "Reachable" means the server accepted a connection. "Unreachable" means the connection was refused or timed out. "Unknown" means the test could not reach a definitive conclusion, often because a firewall dropped the probe silently.
If you find your domain is reachable over IPv4 but unreachable over IPv6, cross-check your firewall rules and confirm that your server software is bound to the IPv6 interface, not just
0.0.0.0
.
Related Tools for DNS and Connectivity Checks
IPv6 reachability is one part of a broader DNS and deliverability picture. If you are also checking email infrastructure, the DMARC Checker and DKIM Checker cover the DNS records that protect your sending domain. For HTTP-level diagnostics, the HTTP Headers Checker shows what a server returns once a connection is established.
FAQ
The tool performs two operations: a DNS lookup for both AAAA (IPv6) and A (IPv4) records, and a TCP connection attempt to any resolved IPv6 addresses. The TCP probe tries port 80 first, then port 443, with a 3-second timeout each. This two-step approach distinguishes between a domain that merely lists an IPv6 address in DNS and one that is actually reachable over IPv6, which are not always the same thing.
An A record maps a domain to a 32-bit IPv4 address (for example, 93.184.216.34). An AAAA record maps a domain to a 128-bit IPv6 address (for example, 2606:2800:220:1:248:1893:25c8:1946). When a client resolves a domain, it requests whichever record type matches its network. A domain needs both record types to be reachable from both IPv4-only and IPv6-only networks. The DNS Lookup tool lets you query either record type individually.
Publishing an AAAA record in DNS does not guarantee the server behind it accepts connections. Common causes of "unreachable" despite a valid AAAA record include: a firewall blocking inbound TCP on port 80 or 443 for IPv6, a web server process bound only to the IPv4 interface (0.0.0.0 rather than ::), or a misconfigured load balancer that handles IPv4 but not IPv6 traffic. Check your server's listening interfaces and firewall rules for IPv6 specifically.
"Unknown" means the TCP probe did not receive a clear accept or reject response within the 3-second timeout. This most often happens when a firewall silently drops packets rather than sending a TCP reset or ICMP unreachable message. From the test server's perspective, the connection simply hangs until it times out. It can also occur if the test server's own routing to that IPv6 prefix is incomplete. In practice, "unknown" should be treated with the same concern as "unreachable" until you confirm the cause.
Dual-stack means a server has both an A record (IPv4) and an AAAA record (IPv6) and accepts connections on both protocols. This is the recommended configuration because the internet is currently split: most fixed-line networks are still primarily IPv4, while many mobile and newer networks use IPv6 by default. A dual-stack site is directly reachable from both without requiring translation layers, which can add latency or introduce failure points.
Not exactly. The connectivity test runs from the pingie.net server and reflects reachability from that server's specific network location and IPv6 routing. A firewall rule that blocks the test server's IP range could produce "unreachable" even if the site is accessible from most other locations. Conversely, a routing issue affecting a specific region may not be caught. Use this tool as a first-pass check, and supplement it with tests from multiple vantage points if you need broader confirmation.
A DNS lookup tool retrieves and displays DNS records for a domain, including AAAA records if they exist. It stops at the DNS layer. This IPv6 checker goes further: after finding AAAA records, it attempts a TCP connection to the resolved IPv6 addresses to verify actual reachability. The DNS Lookup tool is useful when you want to inspect the full zone or query specific record types. This tool is the right choice when you need to confirm whether IPv6 connectivity is live, not just whether the record exists.
The tool queries public DNS resolvers, so it can only see records that are publicly published. Internal or split-horizon DNS zones that are not visible from the public internet will not be resolved. If you are testing a staging environment with a private DNS zone, the tool will return no records for that domain. For those cases, run the connectivity check from a machine that has access to the private DNS zone and network.
Domain names are not stored beyond the duration of the request. The tool processes your input to perform the DNS query and connectivity test, then discards it. No account or login is required to use the tool. For full details on data handling across the site, see the privacy policy .
An IPv4-only result means no AAAA record exists for the domain. To add IPv6 support, you need an IPv6 address assigned to your server or load balancer, and then an AAAA record added to your DNS zone pointing to that address. The exact steps depend on your hosting provider or infrastructure. Many managed hosting platforms and CDNs assign IPv6 addresses automatically and add AAAA records when you enable dual-stack in their settings. After making changes, re-run this check to confirm the record is published and the address is reachable.
The IPv6 Compatibility Checker is available on pingie.net at no cost. No registration is required. You can check as many domains as needed without creating an account.