Yes — fireaware.site has IPv6.

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

This is a saved measurement from 2026-10-31 14:45 UTC. Check fireaware.site live now

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 fireaware.site has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:156e:48f8:2ec5:acd6:f28a answers · 443✓ 2a02:4780:84:6525:d27:e48d:1115:6f04 answers · 443	yes
www over IPv6 www.fireaware.site has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:4b72:176:d96b:6e51:d7e4 answers · 443✓ 2a02:4780:84:571:70e6:d7af:82fc:d489 answers · 443	yes
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. pixel.dns-parking.com ✓byte.dns-parking.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.

https://fireaware.site/ via 2a02:4780:84:156e:48f8:2ec5:acd6:f28a → 302https://fireaware.site/login/login%20with%20db.php via 2a02:4780:84:156e:48f8:2ec5:acd6:f28a → 200

works

Nothing keeping you from an A

Nothing to fix
Show it off: add the badge to your README.
[![IPv6](https://aaaa.bot/badge/fireaware.site.svg)](https://aaaa.bot/fireaware.site)

Check again

fireaware.site Has IPv6

A (IPv4)	84.32.84.162 88.222.222.222
AAAA (IPv6)	2a02:4780:84:156e:48f8:2ec5:acd6:f28a 2a02:4780:84:6525:d27:e48d:1115:6f04

www.fireaware.site Has IPv6

Alias of	www.fireaware.site.cdn.hstgr.net
A (IPv4)	84.32.84.252 88.222.222.106
AAAA (IPv6)	2a02:4780:84:4b72:176:d96b:6e51:d7e4 2a02:4780:84:571:70e6:d7af:82fc:d489

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: fireaware.site
Measured 2026-10-31 14:45:23 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    84.32.84.162, 88.222.222.222
AAAA (IPv6): 2a02:4780:84:156e:48f8:2ec5:acd6:f28a, 2a02:4780:84:6525:d27:e48d:1115:6f04
www AAAA:    2a02:4780:84:4b72:176:d96b:6e51:d7e4, 2a02:4780:84:571:70e6:d7af:82fc:d489

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: fireaware.site has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:156e:48f8:2ec5:acd6:f28a: answers (TCP 443)
    2a02:4780:84:6525:d27:e48d:1115:6f04: answers (TCP 443)
- www over IPv6: www.fireaware.site has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:4b72:176:d96b:6e51:d7e4: answers (TCP 443)
    2a02:4780:84:571:70e6:d7af:82fc:d489: answers (TCP 443)
- 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).

HTTPS over IPv6 (not graded): Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.
    https://fireaware.site/ via 2a02:4780:84:156e:48f8:2ec5:acd6:f28a -> HTTP 302, certificate: valid
    https://fireaware.site/login/login%20with%20db.php via 2a02:4780:84:156e:48f8:2ec5:acd6:f28a -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/PfPVwAaDPs

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

Checked 2026-10-31 14:45:23 UTC. Full DNS report: dns.pizza/domain/fireaware.site · JSON: /api/v1/fireaware.site