safucreative.site publishes IPv6 but doesn't answer on it.

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

IPv6 readiness

Publishes IPv6 but doesn't answer on it — worse than having none.

Website over IPv6 safucreative.site has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2a02:4780:84:aae1:e5a2:23f:385b:7fbe no answer✗ 2a02:4780:84:a631:564b:4223:2faa:c752 no answer	broken
www over IPv6 www.safucreative.site has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2a02:4780:84:cdf8:52c5:bc9c:5933:a99 no answer✗ 2a02:4780:84:466f:b2f3:f18a:d6b3:bdbc no answer	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. horizon.dns-parking.com ✓orbit.dns-parking.com ✓	yes

What's keeping safucreative.site from an A

Fix or remove the AAAA record for safucreative.site
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.
Fix or remove the AAAA record for www.safucreative.site
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

safucreative.site Has IPv6

A (IPv4)	84.32.84.84 88.222.222.75
AAAA (IPv6)	2a02:4780:84:aae1:e5a2:23f:385b:7fbe 2a02:4780:84:a631:564b:4223:2faa:c752

www.safucreative.site Has IPv6

Alias of	www.safucreative.site.cdn.hstgr.net
A (IPv4)	88.222.222.19 2.57.91.159
AAAA (IPv6)	2a02:4780:84:cdf8:52c5:bc9c:5933:a99 2a02:4780:84:466f:b2f3:f18a:d6b3:bdbc

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: safucreative.site
Measured 2026-11-03 07:20:53 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    84.32.84.84, 88.222.222.75
AAAA (IPv6): 2a02:4780:84:aae1:e5a2:23f:385b:7fbe, 2a02:4780:84:a631:564b:4223:2faa:c752
www AAAA:    2a02:4780:84:cdf8:52c5:bc9c:5933:a99, 2a02:4780:84:466f:b2f3:f18a:d6b3:bdbc

Readiness grade F: Publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: safucreative.site has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2a02:4780:84:aae1:e5a2:23f:385b:7fbe: no answer
    2a02:4780:84:a631:564b:4223:2faa:c752: no answer
- www over IPv6: www.safucreative.site has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2a02:4780:84:cdf8:52c5:bc9c:5933:a99: no answer
    2a02:4780:84:466f:b2f3:f18a:d6b3:bdbc: no answer
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.
- Nameservers have IPv6: 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.

Reachability = a TCP connection opened on port 443 (or 80).
No TLS or HTTP request was made.
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/FQkrcW5R4V

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

Checked 2026-11-03 07:20:53 UTC. Full DNS report: dns.pizza/domain/safucreative.site · Age, certificate and blocklists: how.is/safucreative.site · JSON: /api/v1/safucreative.site