IPv6 readiness checker
See whether a domain's website, name servers and mail can be reached over IPv6, and what to add where they cannot.
Results for google.com
IPv6: Ready
google.com works over IPv6.
The website, mail and name servers that exist all have IPv6 addresses, and the ones we could test answered.
WebsitePass
9 IPv6 addresses, answered over IPv6
PassAAAA on google.com
web-aaaa-apexgoogle.com has 1 IPv6 address.
PassAAAA on www.google.com
web-aaaa-wwwwww.google.com has 8 IPv6 addresses.
PassHTTPS works over IPv6
web-https-v6A request over IPv6 to google.com got an answer (200).
PassSame site as over IPv4
web-same-siteSame status and page title on both.
MailPass
1 of 1 MX hosts have IPv6
PassEach mail server has an IPv6 address
mail-mx-aaaa1 of 1 MX hosts have an AAAA record.
UnknownPort 25 answers over IPv6
mail-smtp-v6Not checked yet. LookupOwl doesn't open mail connections (port 25), so this stays unknown.
PassReverse DNS for IPv6 mail hosts
mail-ptr-v61 mail host with IPv6 has a PTR record.
Name serversPass
4 of 4 answer over IPv6
PassEach name server has an IPv6 address
ns-has-aaaa4 of 4 name servers have an AAAA record.
PassEach IPv6 address answers
ns-answers-v64 name servers with an IPv6 address answered a question over IPv6.
PassIPv6 glue where needed
ns-glue-v6The parent zone carries IPv6 glue for ns1.google.com, ns2.google.com, ns3.google.com and 1 more.
Unknown is not a fail. It means DNS alone can't show this.
Reached over IPv6 from our networkThe proof the connection checks rely on.
The website over IPv4 and IPv6
| What | IPv4 | IPv6 |
|---|---|---|
| Status | 200 | 200 |
| Page title | ||
| Final URL | https://www.google.com/ | https://www.google.com/ |
| Certificate | Google Trust Services | Google Trust Services |
| Time | 144 ms | 150 ms |
Same site on both.
Every host we tested
| Host | Role | Addresses |
|---|---|---|
| google.com | Website |
|
| www.google.com | Website |
|
| smtp.google.com | Mail (MX, priority 10) |
|
| ns1.google.com | Name server, answers over IPv6 |
|
| ns2.google.com | Name server, answers over IPv6 |
|
| ns3.google.com | Name server, answers over IPv6 |
|
| ns4.google.com | Name server, answers over IPv6 |
|
Badge
IPv6 ready, google.com, 16 Nov 2026. The date is in the image. Copy the SVG and host it yourself; it is not updated by us.
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 221 28" width="221" height="28" role="img" aria-label="IPv6 ready, google.com, 16 Nov 2026">
<rect width="221" height="28" rx="6" fill="#1b2140"/>
<rect x="58" width="163" height="28" rx="6" fill="#177a49"/>
<rect x="58" width="10" height="28" fill="#177a49"/>
<text x="10" y="18" fill="#ffffff" font-family="sans-serif" font-size="12">IPv6</text>
<text x="68" y="18" fill="#ffffff" font-family="sans-serif" font-size="12">Ready · 16 Nov 2026</text>
</svg>Structured result (JSON) · 6.8 KB
{
"domain": "google.com",
"checkedAt": "2026-11-16T19:29:53.732Z",
"summary": {
"level": "ready",
"text": "google.com works over IPv6.",
"detail": "The website, mail and name servers that exist all have IPv6 addresses, and the ones we could test answered.",
"exists": true,
"layers": {
"dns": "pass",
"web": "pass",
"mail": "pass",
"connectivity": "pass"
},
"egress": "ok"
},
"layers": {
"ns": {
"result": "pass",
"checks": [
{
"id": "ns-has-aaaa",
"level": "pass",
"title": "Each name server has an IPv6 address",
"evidence": "4 of 4 name servers have an AAAA record."
},
{
"id": "ns-answers-v6",
"level": "pass",
"title": "Each IPv6 address answers",
"evidence": "4 name servers with an IPv6 address answered a question over IPv6."
},
{
"id": "ns-glue-v6",
"level": "pass",
"title": "IPv6 glue where needed",
"evidence": "The parent zone carries IPv6 glue for ns1.google.com, ns2.google.com, ns3.google.com and 1 more."
}
],
"servers": [
{
"host": "ns1.google.com",
"v4": [
"216.239.32.10"
],
"v6": [
"2001:4860:4802:32::a"
],
"answersV6": true,
"glueV6": true
},
{
"host": "ns2.google.com",
"v4": [
"216.239.34.10"
],
"v6": [
"2001:4860:4802:34::a"
],
"answersV6": true,
"glueV6": true
},
{
"host": "ns3.google.com",
"v4": [
"216.239.36.10"
],
"v6": [
"2001:4860:4802:36::a"
],
"answersV6": true,
"glueV6": true
},
{
"host": "ns4.google.com",
"v4": [
"216.239.38.10"
],
"v6": [
"2001:4860:4802:38::a"
],
"answersV6": true,
"glueV6": true
}
]
},
"web": {
"result": "pass",
"checks": [
{
"id": "web-aaaa-apex",
"level": "pass",
"title": "AAAA on google.com",
"evidence": "google.com has 1 IPv6 address."
},
{
"id": "web-aaaa-www",
"level": "pass",
"title": "AAAA on www.google.com",
"evidence": "www.google.com has 8 IPv6 addresses."
},
{
"id": "web-https-v6",
"level": "pass",
"title": "HTTPS works over IPv6",
"evidence": "A request over IPv6 to google.com got an answer (200)."
},
{
"id": "web-same-site",
"level": "pass",
"title": "Same site as over IPv4",
"evidence": "Same status and page title on both."
}
],
"hosts": [
{
"host": "google.com",
"cname": null,
"a": [
"142.251.39.206"
],
"aaaa": [
"2a00:1450:4007:809::200e"
],
"https": {
"v4": {
"status": 200,
"finalUrl": "https://www.google.com/",
"title": "Google",
"issuer": "Google Trust Services",
"ms": 144,
"error": null
},
"v6": {
"status": 200,
"finalUrl": "https://www.google.com/",
"title": "Google",
"issuer": "Google Trust Services",
"ms": 150,
"error": null
}
},
"same": true
},
{
"host": "www.google.com",
"cname": null,
"a": [
"142.251.156.119",
"142.251.152.119",
"142.251.157.119",
"142.251.153.119",
"142.251.150.119",
"142.251.155.119",
"142.251.154.119",
"142.251.151.119"
],
"aaaa": [
"2001:4860:482c:7700::",
"2001:4860:482d:7700::",
"2001:4860:482a:7700::",
"2001:4860:4829:7700::",
"2001:4860:4827:7700::",
"2001:4860:4826:7700::",
"2001:4860:4828:7700::",
"2001:4860:482b:7700::"
],
"https": {
"v4": {
"status": 200,
"finalUrl": "https://www.google.com/",
"title": "Google",
"issuer": null,
"ms": 131,
"error": null
},
"v6": {
"status": 200,
"finalUrl": "https://www.google.com/",
"title": "Google",
"issuer": null,
"ms": 104,
"error": null
}
},
"same": true
}
],
"compare": {
"host": "google.com",
"v4": {
"status": 200,
"finalUrl": "https://www.google.com/",
"title": "Google",
"issuer": "Google Trust Services",
"ms": 144,
"error": null
},
"v6": {
"status": 200,
"finalUrl": "https://www.google.com/",
"title": "Google",
"issuer": "Google Trust Services",
"ms": 150,
"error": null
},
"same": true,
"blocked": false,
"slower": false
}
},
"mail": {
"result": "pass",
"state": "mx",
"checks": [
{
"id": "mail-mx-aaaa",
"level": "pass",
"title": "Each mail server has an IPv6 address",
"evidence": "1 of 1 MX hosts have an AAAA record."
},
{
"id": "mail-smtp-v6",
"level": "unknown",
"title": "Port 25 answers over IPv6",
"evidence": "Not checked yet. LookupOwl doesn't open mail connections (port 25), so this stays unknown."
},
{
"id": "mail-ptr-v6",
"level": "pass",
"title": "Reverse DNS for IPv6 mail hosts",
"evidence": "1 mail host with IPv6 has a PTR record."
}
],
"mx": [
{
"host": "smtp.google.com",
"pref": 10,
"a": [
"66.102.1.27",
"66.102.1.26",
"142.250.110.27",
"142.251.168.27",
"74.125.206.27"
],
"aaaa": [
"2a00:1450:400c:c09::1b",
"2a00:1450:400c:c1d::1b",
"2a00:1450:400c:c04::1a",
"2a00:1450:400c:c04::1b"
],
"smtpV6": null,
"ptr": "wm-in-x1b.1e100.net"
}
]
},
"connectivity": {
"result": "pass",
"egress": {
"v6": true
}
}
},
"fixes": [],
"badge": {
"level": "ready"
},
"permalink": "/ipv6-readiness?q=google.com"
}More in DNS · Health checks
Next step
- DNS health checkAre the name servers and records healthy?Check google.com in DNS health check
- Ping over IPv6Does the IPv6 address answer?Check google.com in Ping over IPv6
- Is it down?Does the site open from other countries?Check google.com in Is it down?
What the test covers
IPv6 is the newer kind of internet address. Most visitors still arrive over IPv4, but some networks are IPv6 only, some governments and large buyers ask for IPv6 support, and a broken IPv6 setup can slow down visitors who have both. This page checks a domain from three sides and gives each one its own card with a short checklist.
| Card | What we look at |
|---|---|
| Website | An AAAA record on the domain and on www, then one real HTTPS request over IPv4 and one over IPv6, compared on status, page title, final address, certificate issuer and time. |
An AAAA record on each mail server (MX host), and whether the IPv6 addresses have reverse DNS. We never connect to a mail server, so port 25 over IPv6 shows as not checked yet. | |
| Name servers | An AAAA record on each name server, whether each IPv6 address answers a DNS question, and whether the parent zone carries IPv6 glue for name servers that live inside the domain. |
A fourth line says whether LookupOwl itself could reach the internet over IPv6 for this check. If our own connection fails, we say so and mark the connection checks unknown. We never count that against your domain.
How to read the result
The level is one of three words, counted from the checks and never weighted. A fourth, Could not tell, appears only when our own IPv6 broke during the test.
- Ready: every part that exists has an IPv6 address, and the ones we could test answered.
- Partly ready: something has no IPv6 address, or an address does not work. The headline names the gap.
- Not ready: no IPv6 address anywhere. That is common and calm, so the page shows how to start rather than a wall of red.
How to run it and what to do next
- Enter a domainUse
example.com. A pasted URL or email address is cut down to its domain, and nothing else is kept. This tests a domain, not your own connection. To see whether you have IPv6, use What is my IP. - Open the cards that are not greenEach row says what we found and, where a fix exists, the exact record to add. We never invent your address: the record shows
<your IPv6 address>for you to fill in. - Confirm with other toolsLook at the records themselves with an AAAA lookup, see whether the address answers from many places with Ping over IPv6, and run the DNS health check for the rest of the zone.
In Claude, ChatGPT or Cursor, connect the LookupOwl MCP server and ask whether a domain works over IPv6. The assistant calls ipv6_readiness and gets the level, the layers and the fixes as structured data.
What this test cannot tell you
We test from one network, once. IPv6 can work from some places and not from others, because routes, tunnels and firewalls differ. A pass here is a good sign, not a promise. For a closer look at reachability from several countries, use Is it down.
We also do not open mail connections. Whether a mail server accepts a message over IPv6 on port 25 needs a real SMTP conversation, which this page does not make. The result says "Not checked yet" for that row, and unknown is never a fail.
Questions people ask
Is a missing AAAA record an error?
It is a warning. A name that has no IPv6 address works for everyone on IPv4, but not for networks that only have IPv6, and some public-sector rules ask for IPv6. The page calls it a gap and shows the record to add.
What does it mean when an IPv6 address does not answer?
The domain publishes an AAAA record, but nothing listens on that address, or a firewall blocks it. Browsers and mail servers that try IPv6 first wait for it to time out before they use IPv4. Fix the server or remove the record.
Why does the page say it could not test IPv6 from our side?
LookupOwl's server needs a working IPv6 route to test yours. If that route is down at the moment, we cannot tell whether your site works, and we say so. The DNS facts still show, and the result is not kept, so run it again in a few minutes.
Do I need IPv6 on my mail servers?
Not urgently. Many mail servers retry over IPv4 when IPv6 is missing, so the real cost is low. It matters most if you send to or receive from IPv6-only networks, or if a rule asks for it. Mail hosted by a provider is the provider to ask.
Why do the name servers need IPv6 glue?
When a name server lives inside the domain it serves, such as ns1.example.com for example.com, the parent zone must hand out its address directly. Without an IPv6 address in that glue, resolvers that only speak IPv6 cannot find the name server.
Does the check change anything on my domain?
No. We read public DNS records, ask each name server one question, and request the home page of the website twice, once per address family. We send no mail and change nothing.
What is the badge?
For a Ready or Partly ready result you can copy a small SVG image that says IPv6 ready or IPv6 partly, with the domain and the date of the test. Host it yourself. It is a snapshot and is not updated when your setup changes.
Use it from AI, the API or the command line
Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is ipv6_readiness. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/ipv6-readiness?q=google.com"claude mcp add --transport http lookupowl https://lookupowl.com/mcp