Yes — meta.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 meta.com has an AAAA record and answers on it. ✓ 2a03:2880:f373:8d:face:b00c:0:2 answers · 443	yes
www over IPv6 www.meta.com has an AAAA record and answers on it. ✓ 2a03:2880:f373:8d:face:b00c:0:2 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mx0a-00082601.pphosted.com ✗mxb-00082601.gslb.pphosted.com ✗mx0b-00082601.pphosted.com ✗mxa-00082601.gslb.pphosted.com ✗	no
Nameservers have IPv6 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. d.ns.facebook.com ✓c.ns.facebook.com ✓b.ns.facebook.com ✓a.ns.facebook.com ✓	yes

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

https://meta.com/ via 2a03:2880:f373:8d:face:b00c:0:2 → 301https://www.meta.com/ via 2a03:2880:f373:8d:face:b00c:0:2 → 200

works

What's keeping meta.com from an A

Mail servers without IPv6
mx0a-00082601.pphosted.com, mxb-00082601.gslb.pphosted.com, mx0b-00082601.pphosted.com, mxa-00082601.gslb.pphosted.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

meta.com Has IPv6

A (IPv4)	57.145.2.141
AAAA (IPv6)	2a03:2880:f373:8d:face:b00c:0:2

www.meta.com Has IPv6

Alias of	star.c10r.facebook.com
A (IPv4)	57.145.2.141
AAAA (IPv6)	2a03:2880:f373:8d:face:b00c:0:2

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: meta.com
Measured 2026-10-31 01:04:37 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    57.145.2.141
AAAA (IPv6): 2a03:2880:f373:8d:face:b00c:0:2
www AAAA:    2a03:2880:f373:8d:face:b00c:0:2

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: meta.com has an AAAA record and answers on it.
    2a03:2880:f373:8d:face:b00c:0:2: answers (TCP 443)
- www over IPv6: www.meta.com has an AAAA record and answers on it.
    2a03:2880:f373:8d:face:b00c:0:2: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers 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://meta.com/ via 2a03:2880:f373:8d:face:b00c:0:2 -> HTTP 301, certificate: valid
    https://www.meta.com/ via 2a03:2880:f373:8d:face:b00c:0:2 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/bhh6eP2eLJ

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

Checked 2026-10-31 01:04:37 UTC — one of the top 1,000 sites, re-checked weekly. Re-check now. Full DNS report: dns.pizza/domain/meta.com · JSON: /api/v1/meta.com