Skip to content

Basics

Does my site need IPv6

Most IPv6-only mobile networks translate transparently, so this rarely breaks anything today — but it adds a translation hop for those users, and every managed host publishes AAAA by default. Its absence usually means a hand-configured DNS record.

What 13x checks

This is rule basics.ipv6 in the public registry: Reachable over IPv6. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
Basics
Score weight
2 of the readiness score
Scope
Runs on every audited page
Applies
Only where the market or the page shape makes it relevant

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Add an AAAA record so the domain resolves over IPv6:

Configuration
Type: AAAA   Name: @   Value: <your server's IPv6 address>

On a managed host this is usually a toggle, or automatic once you use their nameservers — Cloudflare, Vercel and Netlify all publish AAAA by default. Its absence generally means a hand-configured A record and no matching AAAA.

Low priority: mobile carriers on IPv6-only networks translate transparently, so nothing is broken today. It removes a translation hop for those users.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More basics checks