Yes — xn--herkunftsnachweisregister-wrme-mtc.com has IPv6.

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

This is a saved measurement from 2026-10-31 17:37 UTC. Check xn--herkunftsnachweisregister-wrme-mtc.com live now

IPv6 readiness

Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.

Website over IPv6 xn--herkunftsnachweisregister-wrme-mtc.com has an AAAA record and answers on it. ✓ 2a03:2a01:a330:5::2 answers · 443	yes
www over IPv6 www.xn--herkunftsnachweisregister-wrme-mtc.com has an AAAA record and answers on it. ✓ 2a03:2a01:a330:5::2 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mx4.agenturserver.de ✗mx2.agenturserver.de ✗mx3.agenturserver.de ✗mx1.agenturserver.de ✗	no
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns01.agenturserver.co ✗ns01.agenturserver.de ✗ns01.agenturserver.it ✗	no

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate: HTTP 200.

https://xn--herkunftsnachweisregister-wrme-mtc.com/ via 2a03:2a01:a330:5::2 → 200

works

What's keeping xn--herkunftsnachweisregister-wrme-mtc.com from an A

Mail servers without IPv6
mx4.agenturserver.de, mx2.agenturserver.de, mx3.agenturserver.de, mx1.agenturserver.de 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.
Nameservers without IPv6
ns01.agenturserver.co, ns01.agenturserver.de, ns01.agenturserver.it all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

xn--herkunftsnachweisregister-wrme-mtc.com Has IPv6

A (IPv4)	185.215.158.186
AAAA (IPv6)	2a03:2a01:a330:5::2

www.xn--herkunftsnachweisregister-wrme-mtc.com Has IPv6

A (IPv4)	185.215.158.186
AAAA (IPv6)	2a03:2a01:a330:5::2

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--herkunftsnachweisregister-wrme-mtc.com
Measured 2026-10-31 17:37:18 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    185.215.158.186
AAAA (IPv6): 2a03:2a01:a330:5::2
www AAAA:    2a03:2a01:a330:5::2

Readiness grade C: Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.
- Website over IPv6: xn--herkunftsnachweisregister-wrme-mtc.com has an AAAA record and answers on it.
    2a03:2a01:a330:5::2: answers (TCP 443)
- www over IPv6: www.xn--herkunftsnachweisregister-wrme-mtc.com has an AAAA record and answers on it.
    2a03:2a01:a330:5::2: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers has an AAAA record.
- Nameservers have IPv6: No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): Loads over IPv6 with a valid certificate: HTTP 200.
    https://xn--herkunftsnachweisregister-wrme-mtc.com/ via 2a03:2a01:a330:5::2 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/OOw-k4vj1Z

Permanent link: aaaa.bot/r/OOw-k4vj1Z · How we measure

Checked 2026-10-31 17:37:18 UTC. Full DNS report: dns.pizza/domain/xn--herkunftsnachweisregister-wrme-mtc.com · JSON: /api/v1/xn--herkunftsnachweisregister-wrme-mtc.com