No — firesdex.pro is IPv4 only.

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

IPv6 readiness

The www address publishes IPv6 but doesn't answer on it — worse than having none.

Website over IPv6 firesdex.pro has no AAAA record.	no
www over IPv6 www.firesdex.pro's AAAA record points at an address that isn't on the public internet, so IPv6 visitors can't reach it. ✗ ::ffff:45.153.219.193 not public	broken
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 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. lina.ns.cloudflare.com ✓memphis.ns.cloudflare.com ✓	yes

What's keeping firesdex.pro from an A

Give firesdex.pro 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.firesdex.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.
Mail servers without IPv6
Your domain's mail goes to its own address, which has no AAAA record.

Check again

firesdex.pro IPv4 only

A (IPv4)	45.153.219.193
AAAA (IPv6)	none

www.firesdex.pro IPv6 only

A (IPv4)	none
AAAA (IPv6)	::ffff:45.153.219.193

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

IPv6 measurement: firesdex.pro
Measured 2026-11-04 22:01:33 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    45.153.219.193
AAAA (IPv6): none
www AAAA:    ::ffff:45.153.219.193

Readiness grade F: The www address publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: firesdex.pro has no AAAA record.
- www over IPv6: www.firesdex.pro's AAAA record points at an address that isn't on the public internet, so IPv6 visitors can't reach it.
    ::ffff:45.153.219.193: not public
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It has no 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/w-GbbK_FGG

Permanent link: aaaa.bot/r/w-GbbK_FGG · How we measure

Checked 2026-11-04 22:01:33 UTC. Full DNS report: dns.pizza/domain/firesdex.pro · Age, certificate and blocklists: how.is/firesdex.pro · JSON: /api/v1/firesdex.pro