usdcbinanceclaim.pro publishes IPv6 but doesn't answer on it.

Has an IPv6 address but no IPv4. Most of the internet can't reach it without a translator.

F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6
usdcbinanceclaim.pro's AAAA record points at an address that isn't on the public internet, so IPv6 visitors can't reach it.
✗ 100:: not public
broken
Mail servers (MX) have IPv6
No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.		yes
Nameservers have IPv6
2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
nick.ns.cloudflare.com ✓sreeni.ns.cloudflare.com ✓
yes
 Which outside scripts, fonts, payments or chat usdcbinanceclaim.pro loads from have no IPv6.
 Load usdcbinanceclaim.pro over IPv6 from up to six other places — a second opinion.

What's keeping usdcbinanceclaim.pro from an A

  1. Fix or remove the AAAA record for usdcbinanceclaim.pro
    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.

Check again

usdcbinanceclaim.pro  IPv6 only

A (IPv4)none
AAAA (IPv6)100::
Copy the evidence — a citation-ready record of this measurement

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

Checked 2026-11-07 20:25:21 UTC. Full DNS report: dns.pizza/domain/usdcbinanceclaim.pro · Age, certificate and blocklists: how.is/usdcbinanceclaim.pro · JSON: /api/v1/usdcbinanceclaim.pro