huawei.com publishes IPv6 but doesn't answer on it.

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

This is a saved measurement from 2026-10-30 22:04 UTC. Check huawei.com live now

IPv6 readiness

Publishes IPv6 but doesn't answer on it — worse than having none.

Website over IPv6 huawei.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2407:c080:17ef:ffff::7274:d206 no answer	broken
www over IPv6 www.huawei.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2600:1408:c400:385::2c15 answers · 443✓ 2600:1408:c400:38e::2c15 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mx7.huawei.com ✗mx5.huawei.com ✗mx8.his.huawei.com ✗mx9.his.huawei.com ✗	no
Nameservers have IPv6 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. nsall3rd.huawei.cn ✓nsall.huawei.com ✓nsallsec.huawei.com ✓nsall4th.huawei.cn ✓	yes

What's keeping huawei.com from an A

Fix or remove the AAAA record for huawei.com
Something published an IPv6 address but nothing answers on it, so IPv6 visitors wait for a timeout first. Either make the server listen on IPv6 (and allow ports 443/80 through its firewall), or delete the AAAA record until it does.
Mail servers without IPv6
mx7.huawei.com, mx5.huawei.com, mx8.his.huawei.com, mx9.his.huawei.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

huawei.com Has IPv6

A (IPv4)	121.37.49.12
AAAA (IPv6)	2407:c080:17ef:ffff::7274:d206

www.huawei.com Has IPv6

Alias of	www.huawei.com.akadns.net → ion-sslv6.huawei.com.edgekey.net → e11285.dsca.akamaiedge.net
A (IPv4)	23.47.27.44
AAAA (IPv6)	2600:1408:c400:385::2c15 2600:1408:c400:38e::2c15

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: huawei.com
Measured 2026-10-30 22:04:34 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    121.37.49.12
AAAA (IPv6): 2407:c080:17ef:ffff::7274:d206
www AAAA:    2600:1408:c400:385::2c15, 2600:1408:c400:38e::2c15

Readiness grade F: Publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: huawei.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2407:c080:17ef:ffff::7274:d206: no answer
- www over IPv6: www.huawei.com has 2 IPv6 addresses and answers on every one we tested.
    2600:1408:c400:385::2c15: answers (TCP 443)
    2600:1408:c400:38e::2c15: 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/-Zgu5-jG1L

Permanent link: aaaa.bot/r/-Zgu5-jG1L · How we measure

Checked 2026-10-30 22:04:34 UTC. Full DNS report: dns.pizza/domain/huawei.com · JSON: /api/v1/huawei.com