No — secure-access-auth5402.support is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
secure-access-auth5402.support has no AAAA record.		no
www over IPv6
www.secure-access-auth5402.support has no AAAA record.		no
Mail servers (MX) have IPv6
No MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record.		no
Nameservers have IPv6
No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.
ns2.ndns.cn ✗ns1.ndns.cn ✗
no

What's keeping secure-access-auth5402.support from an A

  1. Give secure-access-auth5402.support and www.secure-access-auth5402.support 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
  2. Mail servers without IPv6
    Your domain's mail goes to its own address, which has no AAAA record.
  3. Nameservers without IPv6
    ns2.ndns.cn, ns1.ndns.cn 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

secure-access-auth5402.support  IPv4 only

A (IPv4)138.124.79.185
AAAA (IPv6)none

www.secure-access-auth5402.support  IPv4 only

A (IPv4)138.124.79.185
AAAA (IPv6)none

What this means

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

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

Checked 2026-10-31 16:09:49 UTC. Full DNS report: dns.pizza/domain/secure-access-auth5402.support · JSON: /api/v1/secure-access-auth5402.support