Yes — verisign.com has IPv6.

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

This is a saved measurement from 2026-10-31 01:04 UTC. Check verisign.com live now

IPv6 readiness

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

Website over IPv6 verisign.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2620:74:10:2900::45 answers · 443✓ 2620:74:14:3000::40 answers · 443	yes
www over IPv6 www.verisign.com has 3 IPv6 addresses and answers on every one we tested. ✓ 2600:9000:2715:0:9700:c8:4:9d02 answers · 443✓ 2600:9000:2716:0:9700:c8:4:9d02 answers · 443✓ 2600:9000:2717:0:9700:c8:4:9d02 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mail1.verisign.com ✗mail2.verisign.com ✗mail3.verisign.com ✗mail4.verisign.com ✗mail5.verisign.com ✗mail6.verisign.com ✗	no
Nameservers have IPv6 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. av1.nstld.com ✓av2.nstld.com ✓av3.nstld.com ✓av4.nstld.com ✓	yes

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

https://verisign.com/ via 2620:74:10:2900::45 → 301https://www.verisign.com/ via 2600:9000:2715:0:9700:c8:4:9d02 → 200

works

What's keeping verisign.com from an A

Mail servers without IPv6
mail1.verisign.com, mail2.verisign.com, mail3.verisign.com, mail4.verisign.com, mail5.verisign.com, mail6.verisign.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

verisign.com Has IPv6

A (IPv4)	69.58.187.40 209.131.162.145
AAAA (IPv6)	2620:74:10:2900::45 2620:74:14:3000::40

www.verisign.com Has IPv6

A (IPv4)	3.173.21.153 3.173.22.153 3.173.23.153
AAAA (IPv6)	2600:9000:2715:0:9700:c8:4:9d02 2600:9000:2716:0:9700:c8:4:9d02 2600:9000:2717:0:9700:c8:4:9d02

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

A (IPv4):    69.58.187.40, 209.131.162.145
AAAA (IPv6): 2620:74:10:2900::45, 2620:74:14:3000::40
www AAAA:    2600:9000:2715:0:9700:c8:4:9d02, 2600:9000:2716:0:9700:c8:4:9d02, 2600:9000:2717:0:9700:c8:4:9d02

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: verisign.com has 2 IPv6 addresses and answers on every one we tested.
    2620:74:10:2900::45: answers (TCP 443)
    2620:74:14:3000::40: answers (TCP 443)
- www over IPv6: www.verisign.com has 3 IPv6 addresses and answers on every one we tested.
    2600:9000:2715:0:9700:c8:4:9d02: answers (TCP 443)
    2600:9000:2716:0:9700:c8:4:9d02: answers (TCP 443)
    2600:9000:2717:0:9700:c8:4:9d02: 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://verisign.com/ via 2620:74:10:2900::45 -> HTTP 301, certificate: valid
    https://www.verisign.com/ via 2600:9000:2715:0:9700:c8:4:9d02 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/oHN_VCJrXM

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

Checked 2026-10-31 01:04:35 UTC. Full DNS report: dns.pizza/domain/verisign.com · JSON: /api/v1/verisign.com