lamoustache.cloud publishes IPv6 but doesn't answer on it.

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

F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6
lamoustache.cloud has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2001:41d0:404:200::12b9 no answer
broken
Mail servers (MX) have IPv6
None of the mail servers has an AAAA record.
mx1.mail.ovh.net ✗mx2.mail.ovh.net ✗mx3.mail.ovh.net ✗
no
Nameservers have IPv6
2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns103.ovh.net ✓dns103.ovh.net ✓
yes
 Which outside scripts, fonts, payments or chat lamoustache.cloud loads from have no IPv6.
 Load lamoustache.cloud over IPv6 from up to six other places — a second opinion.

What's keeping lamoustache.cloud from an A

  1. Fix or remove the AAAA record for lamoustache.cloud
    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.
  2. Mail servers without IPv6
    mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net 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

lamoustache.cloud  Has IPv6

A (IPv4)217.182.129.124
AAAA (IPv6)2001:41d0:404:200::12b9

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/y6pcgdm7lo · How we measure

Checked 2026-11-05 21:39:15 UTC. Full DNS report: dns.pizza/domain/lamoustache.cloud · Age, certificate and blocklists: how.is/lamoustache.cloud · JSON: /api/v1/lamoustache.cloud