The www address publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6 xn--arcmimarlk-5ub.com has no AAAA record.
no
www over IPv6 www.xn--arcmimarlk-5ub.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2600:1f18:16e:df01::259 no answer✗ 2600:1f18:16e:df01::258 no answer
broken
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.
ns1.natrohost.com ✗ns2.natrohost.com ✗
no
What's keeping xn--arcmimarlk-5ub.com from an A
Give xn--arcmimarlk-5ub.com an IPv6 address Ask your hosting provider for the site's IPv6 address (or the hostname to point at), then publish it as an AAAA record. If your host doesn't offer IPv6, a proxy that does can sit in front. How to add an AAAA record
Fix or remove the AAAA record for www.xn--arcmimarlk-5ub.com 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.
Mail servers without IPv6 mx-02.kurumsaleposta.com, mx-01.kurumsaleposta.com 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 ns1.natrohost.com, ns2.natrohost.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.
Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it
Copy the evidence— a citation-ready record of this measurement