mail.x-server.net 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
mail.x-server.net has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2605:7c00:7:1::9 no answer✗ 2605:7c00:7:1::10 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
3 of 3 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns1.x-server.net ✓ns3.x-server.net ✓ns2.x-server.net ✓
yes
 Which outside scripts, fonts, payments or chat mail.x-server.net loads from have no IPv6.
 Load mail.x-server.net over IPv6 from up to six other places — a second opinion.

What's keeping mail.x-server.net from an A

  1. Fix or remove the AAAA record for mail.x-server.net
    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

mail.x-server.net  Has IPv6

A (IPv4)65.110.6.10
65.110.6.9
AAAA (IPv6)2605:7c00:7:1::9
2605:7c00:7:1::10

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

Checked 2026-11-06 03:18:22 UTC. Full DNS report: dns.pizza/domain/mail.x-server.net · Age, certificate and blocklists: how.is/mail.x-server.net · JSON: /api/v1/mail.x-server.net