Yes — snapkit.com has IPv6.

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

This is a saved measurement from 2026-11-02 14:28 UTC. Check snapkit.com live now

IPv6 readiness

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

Website over IPv6 snapkit.com has 4 IPv6 addresses and answers on every one we tested. ✓ 2001:4860:4802:36::15 answers · 443✓ 2001:4860:4802:38::15 answers · 443✓ 2001:4860:4802:32::15 answers · 443✓ 2001:4860:4802:34::15 answers · 443	yes
www over IPv6 www.snapkit.com 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 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns-1009.awsdns-62.net ✓ns-1158.awsdns-16.org ✓ns-1893.awsdns-44.co.uk ✓ns-279.awsdns-34.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.

https://snapkit.com/ via 2001:4860:4802:36::15 → 301https://developers.snap.com/ via 2001:4860:4802:34::15 → 200

works

What's keeping snapkit.com from an A

www.snapkit.com is an alias of us-central1-gcp.api.sc-gw.com, which has no IPv6
www.snapkit.com is a CNAME, so it can't also have its own AAAA record. Ask whoever runs us-central1-gcp.api.sc-gw.com to enable IPv6 there — or replace the alias with the A and AAAA records they give you. Why some hosts don't offer IPv6

Check again

snapkit.com Has IPv6

A (IPv4)	216.239.32.21 216.239.38.21 216.239.34.21 216.239.36.21
AAAA (IPv6)	2001:4860:4802:36::15 2001:4860:4802:38::15 2001:4860:4802:32::15 2001:4860:4802:34::15

www.snapkit.com IPv4 only

Alias of	us-central1-gcp.api.snapchat.com → us-central1-gcp.api.sc-gw.com
A (IPv4)	35.190.43.134
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: snapkit.com
Measured 2026-11-02 14:28:51 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    216.239.32.21, 216.239.38.21, 216.239.34.21, 216.239.36.21
AAAA (IPv6): 2001:4860:4802:36::15, 2001:4860:4802:38::15, 2001:4860:4802:32::15, 2001:4860:4802:34::15
www AAAA:    none

Readiness grade B: Works over IPv6, with one gap: www doesn't fully work over IPv6.
- Website over IPv6: snapkit.com has 4 IPv6 addresses and answers on every one we tested.
    2001:4860:4802:36::15: answers (TCP 443)
    2001:4860:4802:38::15: answers (TCP 443)
    2001:4860:4802:32::15: answers (TCP 443)
    2001:4860:4802:34::15: answers (TCP 443)
- www over IPv6: www.snapkit.com 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: 4 of 4 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): Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.
    https://snapkit.com/ via 2001:4860:4802:36::15 -> HTTP 301, certificate: valid
    https://developers.snap.com/ via 2001:4860:4802:34::15 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/VO2fnvzCZN

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

Checked 2026-11-02 14:28:51 UTC. Full DNS report: dns.pizza/domain/snapkit.com · Age, certificate and blocklists: how.is/snapkit.com · JSON: /api/v1/snapkit.com