Why doesn't my site have IPv6?
Usually because your hosting platform doesn't give customer sites an IPv6 address, and nothing in your DNS can add one.
A site has IPv6 only if the servers answering for it have IPv6 addresses and those addresses are published as AAAA records. On most platforms you point your domain at a hostname the platform gives you. If that hostname has no AAAA, neither does your site.
The big platforms, checked live
Does each hostname have an AAAA record right now? Measured 2026-10-29 23:24 UTC (cached up to five minutes). A platform's own website having IPv6 doesn't mean customer sites get it — compare the two rows for Netlify.
| Platform and hostname | IPv6? |
|---|---|
| Vercel · where customer domains point (CNAME) cname.vercel-dns.com | no |
| Vercel · Vercel's own website vercel.com | no |
| Netlify · where customer root domains point apex-loadbalancer.netlify.com | no |
| Netlify · Netlify's own website netlify.com | yes |
| GitHub Pages · the github.io domain github.io | no |
| GitHub Pages · GitHub Pages' own site pages.github.com | yes |
| Cloudflare · Cloudflare's own website cloudflare.com | yes |
| Fly.io · Fly's own website fly.io | yes |
| Render · Render's own website render.com | no |
| Heroku · Heroku's own website heroku.com | yes |
| Railway · Railway's own website railway.com | no |
What you can do
- Put an IPv6-capable proxy in front. A CDN that publishes its own AAAA records, such as Cloudflare's proxied DNS, serves your site over IPv6 and talks to your host over IPv4.
- Host somewhere that offers IPv6 on the path your site uses. Check the exact hostname or address they tell you to point at.
- Do nothing, knowingly. IPv6-only visitors on carriers with NAT64 still reach IPv4-only sites through the carrier's translator. You lose directness, not reach — for now.
Check your own: aaaa.bot or curl aaaa.bot/yourdomain.com.