Yes — xn--ssame-acces-bbb.com has IPv6.

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

IPv6 readiness

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

Website over IPv6 xn--ssame-acces-bbb.com has an AAAA record and answers on it. ✓ 2001:41d0:801:2000::785f answers · 443	yes
www over IPv6 www.xn--ssame-acces-bbb.com has an AAAA record and answers on it. ✓ 2001:41d0:801:2000::785f answers · 443	yes
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 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns200.anycast.me ✗dns200.anycast.me ✗	no

HTTPS over IPv6 · not part of the grade yet
xn--ssame-acces-bbb.com didn't complete an HTTPS request over IPv6 (ERR_SSL_TLSV1_UNRECOGNIZED_NAME).

https://xn--ssame-acces-bbb.com/ via 2001:41d0:801:2000::785f · ERR_SSL_TLSV1_UNRECOGNIZED_NAME

What's keeping xn--ssame-acces-bbb.com from an A

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.
Nameservers without IPv6
ns200.anycast.me, dns200.anycast.me 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--ssame-acces-bbb.com Has IPv6

A (IPv4)	57.129.170.4
AAAA (IPv6)	2001:41d0:801:2000::785f

www.xn--ssame-acces-bbb.com Has IPv6

A (IPv4)	57.129.170.4
AAAA (IPv6)	2001:41d0:801:2000::785f

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--ssame-acces-bbb.com
Measured 2026-11-04 04:55:43 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    57.129.170.4
AAAA (IPv6): 2001:41d0:801:2000::785f
www AAAA:    2001:41d0:801:2000::785f

Readiness grade C: Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.
- Website over IPv6: xn--ssame-acces-bbb.com has an AAAA record and answers on it.
    2001:41d0:801:2000::785f: answers (TCP 443)
- www over IPv6: www.xn--ssame-acces-bbb.com has an AAAA record and answers on it.
    2001:41d0:801:2000::785f: 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): xn--ssame-acces-bbb.com didn't complete an HTTPS request over IPv6 (ERR_SSL_TLSV1_UNRECOGNIZED_NAME).
    https://xn--ssame-acces-bbb.com/ via 2001:41d0:801:2000::785f (ERR_SSL_TLSV1_UNRECOGNIZED_NAME)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/2rA7wuHSjn

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

Checked 2026-11-04 04:55:43 UTC. Full DNS report: dns.pizza/domain/xn--ssame-acces-bbb.com · Age, certificate and blocklists: how.is/xn--ssame-acces-bbb.com · JSON: /api/v1/xn--ssame-acces-bbb.com