Yes — xn--karen-schngut-qmb.com has IPv6.

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

This is a saved measurement from 2026-11-01 09:36 UTC. Check xn--karen-schngut-qmb.com live now

IPv6 readiness

Works over IPv6, with one gap: its mail servers lack IPv6.

Website over IPv6 xn--karen-schngut-qmb.com has an AAAA record and answers on it. ✓ 2a03:4000:30:81b8::13:3564 answers · 443	yes
www over IPv6 www.xn--karen-schngut-qmb.com has an AAAA record and answers on it. ✓ 2a03:4000:30:81b8::13:3564 answers · 443	yes
Mail servers (MX) have IPv6 At least one mail server has no AAAA record (1 of 2 checked do). mail.xn--karen-schngut-qmb.com ✗mx2e30.netcup.net ✓	partly
Nameservers have IPv6 5 of 5 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. netcup.firstns.cc ✓netcup.thirdns.de ✓netcup.fourthns.systems ✓netcup.secondns.at ✓netcup.fifthns.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
The certificate served over IPv6 at 2a03:4000:30:81b8::13:3564 isn't valid for xn--karen-schngut-qmb.com: CERT_HAS_EXPIRED.

https://xn--karen-schngut-qmb.com/ via 2a03:4000:30:81b8::13:3564 · CERT_HAS_EXPIRED

problem

What's keeping xn--karen-schngut-qmb.com from an A

The certificate served over IPv6 is wrong
The certificate served over IPv6 at 2a03:4000:30:81b8::13:3564 isn't valid for xn--karen-schngut-qmb.com: CERT_HAS_EXPIRED. Often the IPv6 address points at a different server (or an old one) than IPv4 does. Make sure 2a03:4000:30:81b8::13:3564 serves the same certificate as your IPv4 address.
Mail servers without IPv6
mail.xn--karen-schngut-qmb.com has no AAAA record, so mail from IPv6-only servers can't reach it directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

xn--karen-schngut-qmb.com Has IPv6

A (IPv4)	91.204.46.46
AAAA (IPv6)	2a03:4000:30:81b8::13:3564

www.xn--karen-schngut-qmb.com Has IPv6

A (IPv4)	91.204.46.46
AAAA (IPv6)	2a03:4000:30:81b8::13:3564

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: xn--karen-schngut-qmb.com
Measured 2026-11-01 09:36:24 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    91.204.46.46
AAAA (IPv6): 2a03:4000:30:81b8::13:3564
www AAAA:    2a03:4000:30:81b8::13:3564

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: xn--karen-schngut-qmb.com has an AAAA record and answers on it.
    2a03:4000:30:81b8::13:3564: answers (TCP 443)
- www over IPv6: www.xn--karen-schngut-qmb.com has an AAAA record and answers on it.
    2a03:4000:30:81b8::13:3564: answers (TCP 443)
- Mail servers (MX) have IPv6: At least one mail server has no AAAA record (1 of 2 checked do).
- Nameservers have IPv6: 5 of 5 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).

HTTPS over IPv6 (not graded): The certificate served over IPv6 at 2a03:4000:30:81b8::13:3564 isn't valid for xn--karen-schngut-qmb.com: CERT_HAS_EXPIRED.
    https://xn--karen-schngut-qmb.com/ via 2a03:4000:30:81b8::13:3564, certificate: CERT_HAS_EXPIRED
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/CajiTYwZVD

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

Checked 2026-11-01 09:36:24 UTC. Full DNS report: dns.pizza/domain/xn--karen-schngut-qmb.com · JSON: /api/v1/xn--karen-schngut-qmb.com