Yes — metamasksecurity.com 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 metamasksecurity.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::6815:2001 answers · 443✓ 2606:4700:3030::6815:1001 answers · 443	yes
www over IPv6 www.metamasksecurity.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::6815:2001 answers · 443✓ 2606:4700:3030::6815:1001 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. _dc-mx.03b7f80d6427.metamasksecurity.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. amanda.ns.cloudflare.com ✓marvin.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate: HTTP 403.

https://metamasksecurity.com/ via 2606:4700:3030::6815:2001 → 403

works

What's keeping metamasksecurity.com from an A

Mail servers without IPv6
_dc-mx.03b7f80d6427.metamasksecurity.com has no AAAA record, so mail from IPv6-only servers can't reach it directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

metamasksecurity.com Has IPv6

A (IPv4)	104.21.32.1 104.21.16.1
AAAA (IPv6)	2606:4700:3030::6815:2001 2606:4700:3030::6815:1001

www.metamasksecurity.com Has IPv6

A (IPv4)	104.21.16.1 104.21.32.1
AAAA (IPv6)	2606:4700:3030::6815:2001 2606:4700:3030::6815:1001

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: metamasksecurity.com
Measured 2026-11-10 02:16:17 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.32.1, 104.21.16.1
AAAA (IPv6): 2606:4700:3030::6815:2001, 2606:4700:3030::6815:1001
www AAAA:    2606:4700:3030::6815:2001, 2606:4700:3030::6815:1001

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: metamasksecurity.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::6815:2001: answers (TCP 443)
    2606:4700:3030::6815:1001: answers (TCP 443)
- www over IPv6: www.metamasksecurity.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::6815:2001: answers (TCP 443)
    2606:4700:3030::6815:1001: 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): Loads over IPv6 with a valid certificate: HTTP 403.
    https://metamasksecurity.com/ via 2606:4700:3030::6815:2001 -> HTTP 403, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/9-K6SmVKuV

Permanent link: aaaa.bot/r/9-K6SmVKuV · How we measure

Checked 2026-11-10 02:16:17 UTC. Full DNS report: dns.pizza/domain/metamasksecurity.com · Age, certificate and blocklists: how.is/metamasksecurity.com · JSON: /api/v1/metamasksecurity.com