Yes — fortunesholdings.autos has IPv6.

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

This is a saved measurement from 2026-11-01 05:56 UTC. Check fortunesholdings.autos live now

IPv6 readiness

Works over IPv6, with one gap: its mail servers lack IPv6.

Website over IPv6 fortunesholdings.autos has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:4a:e6cd:bd:30cd:3b60:6394 answers · 443✓ 2a02:4780:4b:5178:b8b8:fc3b:d61b:a63 answers · 443	yes
www over IPv6 www.fortunesholdings.autos has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:1c43:5fb8:1044:4ad6:bd3 answers · 443✓ 2a02:4780:84:4144:d8d2:11f5:994f:b11 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mail.fortunesholdings.autos ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. dns30.hichina.com ✓dns29.hichina.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
fortunesholdings.autos didn't complete an HTTPS request over IPv6 (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR).

https://fortunesholdings.autos/ via 2a02:4780:4a:e6cd:bd:30cd:3b60:6394 · ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR

What's keeping fortunesholdings.autos from an A

Mail servers without IPv6
mail.fortunesholdings.autos has no AAAA record, so mail from IPv6-only servers can't reach it directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

fortunesholdings.autos Has IPv6

Alias of	connect.hostinger.com → connect.hstgr.net
A (IPv4)	2.57.91.96 88.222.222.161
AAAA (IPv6)	2a02:4780:4a:e6cd:bd:30cd:3b60:6394 2a02:4780:4b:5178:b8b8:fc3b:d61b:a63

www.fortunesholdings.autos Has IPv6

Alias of	connect.hostinger.com → connect.hstgr.net
A (IPv4)	84.32.84.228 2.57.91.94
AAAA (IPv6)	2a02:4780:84:1c43:5fb8:1044:4ad6:bd3 2a02:4780:84:4144:d8d2:11f5:994f:b11

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: fortunesholdings.autos
Measured 2026-11-01 05:56:04 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    2.57.91.96, 88.222.222.161
AAAA (IPv6): 2a02:4780:4a:e6cd:bd:30cd:3b60:6394, 2a02:4780:4b:5178:b8b8:fc3b:d61b:a63
www AAAA:    2a02:4780:84:1c43:5fb8:1044:4ad6:bd3, 2a02:4780:84:4144:d8d2:11f5:994f:b11

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: fortunesholdings.autos has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:4a:e6cd:bd:30cd:3b60:6394: answers (TCP 443)
    2a02:4780:4b:5178:b8b8:fc3b:d61b:a63: answers (TCP 443)
- www over IPv6: www.fortunesholdings.autos has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:1c43:5fb8:1044:4ad6:bd3: answers (TCP 443)
    2a02:4780:84:4144:d8d2:11f5:994f:b11: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers 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): fortunesholdings.autos didn't complete an HTTPS request over IPv6 (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR).
    https://fortunesholdings.autos/ via 2a02:4780:4a:e6cd:bd:30cd:3b60:6394 (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/imtpc-zH18

Permanent link: aaaa.bot/r/imtpc-zH18 · How we measure

Checked 2026-11-01 05:56:04 UTC. Full DNS report: dns.pizza/domain/fortunesholdings.autos · JSON: /api/v1/fortunesholdings.autos