Yes — blue-lock-rivals-wiki.wiki has IPv6.

Has both IPv4 (A) and IPv6 (AAAA) addresses.

IPv6 readiness

Works over IPv6, with one gap: www doesn't fully work over IPv6.

Website over IPv6 blue-lock-rivals-wiki.wiki has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3034::6815:3cd8 answers · 443✓ 2606:4700:3037::ac43:c9cc answers · 443	yes
www over IPv6 www.blue-lock-rivals-wiki.wiki has no AAAA record.	no
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.	yes
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. gabe.ns.cloudflare.com ✓pearl.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Redirects to www.blue-lock-rivals-wiki.wiki, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.

https://blue-lock-rivals-wiki.wiki/ via 2606:4700:3034::6815:3cd8 → 301https://www.blue-lock-rivals-wiki.wiki/ · redirects to www.blue-lock-rivals-wiki.wiki, which has no IPv6 address

problem

What's keeping blue-lock-rivals-wiki.wiki from an A

www.blue-lock-rivals-wiki.wiki is hosted on Vercel, which has no IPv6
It points at cname.vercel-dns.com, and that name has no AAAA record — so nothing you add in your own DNS can give it IPv6. Put an IPv6-capable proxy in front (Cloudflare's proxied DNS does this), or host somewhere that offers IPv6. Which platforms offer IPv6
A redirect leads off IPv6
Redirects to www.blue-lock-rivals-wiki.wiki, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all. Give the redirect target IPv6 too, or redirect somewhere that has it.

Check again

blue-lock-rivals-wiki.wiki Has IPv6

A (IPv4)	172.67.201.204 104.21.60.216
AAAA (IPv6)	2606:4700:3034::6815:3cd8 2606:4700:3037::ac43:c9cc

www.blue-lock-rivals-wiki.wiki IPv4 only

Alias of	cname.vercel-dns.com
A (IPv4)	66.33.60.66 76.76.21.142
AAAA (IPv6)	none

Browsers on dual-stack networks will usually pick IPv6 here (the "Happy Eyeballs" algorithm races both and prefers v6).

Copy the evidence — a citation-ready record of this measurement

IPv6 measurement: blue-lock-rivals-wiki.wiki
Measured 2026-11-04 23:28:22 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    172.67.201.204, 104.21.60.216
AAAA (IPv6): 2606:4700:3034::6815:3cd8, 2606:4700:3037::ac43:c9cc
www AAAA:    none

Readiness grade B: Works over IPv6, with one gap: www doesn't fully work over IPv6.
- Website over IPv6: blue-lock-rivals-wiki.wiki has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3034::6815:3cd8: answers (TCP 443)
    2606:4700:3037::ac43:c9cc: answers (TCP 443)
- www over IPv6: www.blue-lock-rivals-wiki.wiki has no AAAA record.
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.
- Nameservers have IPv6: 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): Redirects to www.blue-lock-rivals-wiki.wiki, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.
    https://blue-lock-rivals-wiki.wiki/ via 2606:4700:3034::6815:3cd8 -> HTTP 301, certificate: valid
    https://www.blue-lock-rivals-wiki.wiki/ (redirects to www.blue-lock-rivals-wiki.wiki, which has no IPv6 address)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/M-rMCBhrzJ

Permanent link: aaaa.bot/r/M-rMCBhrzJ · How we measure

Checked 2026-11-04 23:28:22 UTC. Full DNS report: dns.pizza/domain/blue-lock-rivals-wiki.wiki · Age, certificate and blocklists: how.is/blue-lock-rivals-wiki.wiki · JSON: /api/v1/blue-lock-rivals-wiki.wiki