No — symantec.com is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

This is a saved measurement from 2026-11-01 16:52 UTC. Check symantec.com live now

IPv6 readiness

The website has no IPv6.

Website over IPv6 symantec.com has no AAAA record.	no
www over IPv6 www.symantec.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:4403::6812:256f answers · 443✓ 2606:4700:4405::ac40:9691 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. cluster4.us.messagelabs.com ✗cluster4a.us.messagelabs.com ✗	no
Nameservers have IPv6 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. edns161.ultradns.biz ✓edns161.ultradns.com ✓edns161.ultradns.net ✓edns161.ultradns.org ✓	yes

What's keeping symantec.com from an A

Give symantec.com an IPv6 address
Ask your hosting provider for the site's IPv6 address (or the hostname to point at), then publish it as an AAAA record. If your host doesn't offer IPv6, a proxy that does can sit in front. How to add an AAAA record
Mail servers without IPv6
cluster4.us.messagelabs.com, cluster4a.us.messagelabs.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

symantec.com IPv4 only

A (IPv4)	54.68.22.26 52.13.171.212 50.112.202.115
AAAA (IPv6)	none

www.symantec.com Has IPv6

Alias of	cdn.broadcom.com → www.broadcom.com.cdn.cloudflare.net
A (IPv4)	104.18.37.111 172.64.150.145
AAAA (IPv6)	2606:4700:4403::6812:256f 2606:4700:4405::ac40:9691

What this means

Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it

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

IPv6 measurement: symantec.com
Measured 2026-11-01 16:52:26 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    54.68.22.26, 52.13.171.212, 50.112.202.115
AAAA (IPv6): none
www AAAA:    2606:4700:4403::6812:256f, 2606:4700:4405::ac40:9691

Readiness grade D: The website has no IPv6.
- Website over IPv6: symantec.com has no AAAA record.
- www over IPv6: www.symantec.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:4403::6812:256f: answers (TCP 443)
    2606:4700:4405::ac40:9691: 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).
No TLS or HTTP request was made.
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/Nk1UN6w_zO

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

Checked 2026-11-01 16:52:26 UTC. Full DNS report: dns.pizza/domain/symantec.com · JSON: /api/v1/symantec.com