Yes — sunflowerspk.shop has IPv6.

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

IPv6 readiness

Works over IPv6, with one gap: its mail servers lack IPv6.

Website over IPv6 sunflowerspk.shop has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3035::6815:296b answers · 443✓ 2606:4700:3037::ac43:a46d answers · 443	yes
www over IPv6 www.sunflowerspk.shop has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3035::6815:296b answers · 443✓ 2606:4700:3037::ac43:a46d answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. eforward1.registrar-servers.com ✗eforward2.registrar-servers.com ✗eforward3.registrar-servers.com ✗eforward4.registrar-servers.com ✗eforward5.registrar-servers.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. dns1.registrar-servers.com ✓dns2.registrar-servers.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
sunflowerspk.shop didn't complete an HTTPS request over IPv6 (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE).

https://sunflowerspk.shop/ via 2606:4700:3035::6815:296b · ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE

What's keeping sunflowerspk.shop from an A

Mail servers without IPv6
eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com, eforward4.registrar-servers.com, eforward5.registrar-servers.com have no AAAA record, so mail from IPv6-only servers can't reach them directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

sunflowerspk.shop Has IPv6

A (IPv4)	104.21.41.107 172.67.164.109
AAAA (IPv6)	2606:4700:3035::6815:296b 2606:4700:3037::ac43:a46d

www.sunflowerspk.shop Has IPv6

Alias of	stores.anoc.pk
A (IPv4)	172.67.164.109 104.21.41.107
AAAA (IPv6)	2606:4700:3035::6815:296b 2606:4700:3037::ac43:a46d

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: sunflowerspk.shop
Measured 2026-11-06 16:55:29 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.41.107, 172.67.164.109
AAAA (IPv6): 2606:4700:3035::6815:296b, 2606:4700:3037::ac43:a46d
www AAAA:    2606:4700:3035::6815:296b, 2606:4700:3037::ac43:a46d

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: sunflowerspk.shop has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3035::6815:296b: answers (TCP 443)
    2606:4700:3037::ac43:a46d: answers (TCP 443)
- www over IPv6: www.sunflowerspk.shop has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3035::6815:296b: answers (TCP 443)
    2606:4700:3037::ac43:a46d: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers 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): sunflowerspk.shop didn't complete an HTTPS request over IPv6 (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE).
    https://sunflowerspk.shop/ via 2606:4700:3035::6815:296b (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/DLP64CuheY

Permanent link: aaaa.bot/r/DLP64CuheY · How we measure

Checked 2026-11-06 16:55:29 UTC. Full DNS report: dns.pizza/domain/sunflowerspk.shop · Age, certificate and blocklists: how.is/sunflowerspk.shop · JSON: /api/v1/sunflowerspk.shop