ns1.ifortuna.cz publishes IPv6 but doesn't answer on it.

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

Measured 2026-11-14 20:53 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check ns1.ifortuna.cz now

F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6
ns1.ifortuna.cz has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2a06:fb00:1::1:96 no answer
broken
Mail servers (MX) have IPv6
No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.		yes
Nameservers have IPv6
2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
kipp.ns.cloudflare.com ✓zara.ns.cloudflare.com ✓
yes

Probes on other continents couldn't connect either, so this isn't only our view.

First measured 2026-11-14; last confirmed 2026-11-14.

 Which outside scripts, fonts, payments or chat ns1.ifortuna.cz loads from have no IPv6.
 Load ns1.ifortuna.cz over IPv6 from up to six other places — a second opinion.

What's keeping ns1.ifortuna.cz from an A

  1. Fix or remove the AAAA record for ns1.ifortuna.cz
    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.

Check again

ns1.ifortuna.cz  Has IPv6

A (IPv4)185.136.96.96
AAAA (IPv6)2a06:fb00:1::1:96

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

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

Checked 2026-11-14 20:53:39 UTC. Full DNS report: dns.pizza/domain/ns1.ifortuna.cz · Age, certificate and blocklists: how.is/ns1.ifortuna.cz · JSON: /api/v1/ns1.ifortuna.cz