Yes — xn--farklegitimnoktas-gvcm.com has IPv6.

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

This is a saved measurement from 2026-11-01 15:40 UTC. Check xn--farklegitimnoktas-gvcm.com live now

IPv6 readiness

Works over IPv6, with one gap: its nameservers lack IPv6.

Website over IPv6 xn--farklegitimnoktas-gvcm.com has an AAAA record and answers on it. ✓ 2a06:41c0:1:32::4ef answers · 443	yes
www over IPv6 www.xn--farklegitimnoktas-gvcm.com has an AAAA record and answers on it. ✓ 2a06:41c0:1:32::4ef answers · 443	yes
Mail servers (MX) have IPv6 Every mail server has an AAAA record. xn--farklegitimnoktas-gvcm.com ✓	yes
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns11.guzelhosting.com ✗ns1.guzelhosting.com ✗ns2.guzelhosting.com ✗ns12.guzelhosting.com ✗	no

HTTPS over IPv6 · not part of the grade yet
The certificate served over IPv6 at 2a06:41c0:1:32::4ef isn't valid for xn--farklegitimnoktas-gvcm.com: DEPTH_ZERO_SELF_SIGNED_CERT.

https://xn--farklegitimnoktas-gvcm.com/ via 2a06:41c0:1:32::4ef · DEPTH_ZERO_SELF_SIGNED_CERT

problem

What's keeping xn--farklegitimnoktas-gvcm.com from an A

The certificate served over IPv6 is wrong
The certificate served over IPv6 at 2a06:41c0:1:32::4ef isn't valid for xn--farklegitimnoktas-gvcm.com: DEPTH_ZERO_SELF_SIGNED_CERT. Often the IPv6 address points at a different server (or an old one) than IPv4 does. Make sure 2a06:41c0:1:32::4ef serves the same certificate as your IPv4 address.
Nameservers without IPv6
ns11.guzelhosting.com, ns1.guzelhosting.com, ns2.guzelhosting.com, ns12.guzelhosting.com 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--farklegitimnoktas-gvcm.com Has IPv6

A (IPv4)	46.45.136.67
AAAA (IPv6)	2a06:41c0:1:32::4ef

www.xn--farklegitimnoktas-gvcm.com Has IPv6

Alias of	xn--farklegitimnoktas-gvcm.com
A (IPv4)	46.45.136.67
AAAA (IPv6)	2a06:41c0:1:32::4ef

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--farklegitimnoktas-gvcm.com
Measured 2026-11-01 15:40:09 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    46.45.136.67
AAAA (IPv6): 2a06:41c0:1:32::4ef
www AAAA:    2a06:41c0:1:32::4ef

Readiness grade B: Works over IPv6, with one gap: its nameservers lack IPv6.
- Website over IPv6: xn--farklegitimnoktas-gvcm.com has an AAAA record and answers on it.
    2a06:41c0:1:32::4ef: answers (TCP 443)
- www over IPv6: www.xn--farklegitimnoktas-gvcm.com has an AAAA record and answers on it.
    2a06:41c0:1:32::4ef: answers (TCP 443)
- Mail servers (MX) have IPv6: Every mail server 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): The certificate served over IPv6 at 2a06:41c0:1:32::4ef isn't valid for xn--farklegitimnoktas-gvcm.com: DEPTH_ZERO_SELF_SIGNED_CERT.
    https://xn--farklegitimnoktas-gvcm.com/ via 2a06:41c0:1:32::4ef, certificate: DEPTH_ZERO_SELF_SIGNED_CERT
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/LJHZgh8OTI

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

Checked 2026-11-01 15:40:09 UTC. Full DNS report: dns.pizza/domain/xn--farklegitimnoktas-gvcm.com · JSON: /api/v1/xn--farklegitimnoktas-gvcm.com