vianet.com.np publishes IPv6 but doesn't answer on it.

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

This is a saved measurement from 2026-11-15 15:50 UTC. Check vianet.com.np live now

IPv6 readiness

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

Website over IPv6 vianet.com.np has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2404:7c00:1:400::2 no answer	broken
www over IPv6 www.vianet.com.np has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2404:7c00:1:400::2 no answer	broken
Mail servers (MX) have IPv6 At least one mail server has no AAAA record (1 of 3 checked do). mx-1.vianet.com.np ✗mx-2.vianet.com.np ✗vianet-com-np.mail.protection.outlook.com ✓	partly
Nameservers have IPv6 3 of 3 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. dns1.vianet.com.np ✓dns2.vianet.com.np ✓anyns.pch.net ✓	yes

What's keeping vianet.com.np from an A

Fix or remove the AAAA record for vianet.com.np
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.
Fix or remove the AAAA record for www.vianet.com.np
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
mx-1.vianet.com.np, mx-2.vianet.com.np 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

vianet.com.np Has IPv6

A (IPv4)	43.245.84.10
AAAA (IPv6)	2404:7c00:1:400::2

www.vianet.com.np Has IPv6

A (IPv4)	43.245.84.10
AAAA (IPv6)	2404:7c00:1:400::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: vianet.com.np
Measured 2026-11-15 15:50:12 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    43.245.84.10
AAAA (IPv6): 2404:7c00:1:400::2
www AAAA:    2404:7c00:1:400::2

Readiness grade F: Publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: vianet.com.np has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2404:7c00:1:400::2: no answer
- www over IPv6: www.vianet.com.np has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2404:7c00:1:400::2: no answer
- Mail servers (MX) have IPv6: At least one mail server has no AAAA record (1 of 3 checked do).
- Nameservers have IPv6: 3 of 3 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/-CXuDqsKyZ

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

Checked 2026-11-15 15:50:12 UTC. Full DNS report: dns.pizza/domain/vianet.com.np · Age, certificate and blocklists: how.is/vianet.com.np · JSON: /api/v1/vianet.com.np