timeweb.ru 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 23:04 UTC. Check timeweb.ru live now

IPv6 readiness

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

Website over IPv6 timeweb.ru has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2a03:6f00:1:2::5c35:7471 no answer	broken
www over IPv6 www.timeweb.ru has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2a03:6f00:1:2::5c35:7471 no answer	broken
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mx3.timeweb.ru ✗mx4.timeweb.ru ✗	no
Nameservers have IPv6 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns3.timeweb.org ✓ns1.timeweb.ru ✓ns4.timeweb.org ✓ns2.timeweb.ru ✓	yes

What's keeping timeweb.ru from an A

Fix or remove the AAAA record for timeweb.ru
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.timeweb.ru
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
mx3.timeweb.ru, mx4.timeweb.ru 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

timeweb.ru Has IPv6

A (IPv4)	185.65.148.89
AAAA (IPv6)	2a03:6f00:1:2::5c35:7471

www.timeweb.ru Has IPv6

A (IPv4)	185.65.148.89
AAAA (IPv6)	2a03:6f00:1:2::5c35:7471

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: timeweb.ru
Measured 2026-10-30 23:04:32 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    185.65.148.89
AAAA (IPv6): 2a03:6f00:1:2::5c35:7471
www AAAA:    2a03:6f00:1:2::5c35:7471

Readiness grade F: Publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: timeweb.ru has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2a03:6f00:1:2::5c35:7471: no answer
- www over IPv6: www.timeweb.ru has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2a03:6f00:1:2::5c35:7471: no answer
- 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/11cnIkFmmM

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

Checked 2026-10-30 23:04:32 UTC. Full DNS report: dns.pizza/domain/timeweb.ru · JSON: /api/v1/timeweb.ru