Yes — dbzgt123.space has IPv6.

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

IPv6 readiness

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

Website over IPv6 dbzgt123.space has 3 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:20::681a:a2d answers · 443✓ 2606:4700:20::ac43:4ae1 answers · 443✓ 2606:4700:20::681a:b2d answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. eforward1.registrar-servers.com ✗eforward2.registrar-servers.com ✗eforward3.registrar-servers.com ✗eforward4.registrar-servers.com ✗eforward5.registrar-servers.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. dns1.registrar-servers.com ✓dns2.registrar-servers.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
dbzgt123.space didn't complete an HTTPS request over IPv6 (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE).

https://dbzgt123.space/ via 2606:4700:20::681a:a2d · ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE

What's keeping dbzgt123.space from an A

Mail servers without IPv6
eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com, eforward4.registrar-servers.com, eforward5.registrar-servers.com have no AAAA record, so mail from IPv6-only servers can't reach them directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

dbzgt123.space Has IPv6

Alias of	c-loud.xyz
A (IPv4)	104.26.10.45 172.67.74.225 104.26.11.45
AAAA (IPv6)	2606:4700:20::681a:a2d 2606:4700:20::ac43:4ae1 2606:4700:20::681a:b2d

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: dbzgt123.space
Measured 2026-11-11 22:09:34 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.26.10.45, 172.67.74.225, 104.26.11.45
AAAA (IPv6): 2606:4700:20::681a:a2d, 2606:4700:20::ac43:4ae1, 2606:4700:20::681a:b2d

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: dbzgt123.space has 3 IPv6 addresses and answers on every one we tested.
    2606:4700:20::681a:a2d: answers (TCP 443)
    2606:4700:20::ac43:4ae1: answers (TCP 443)
    2606:4700:20::681a:b2d: 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): dbzgt123.space didn't complete an HTTPS request over IPv6 (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE).
    https://dbzgt123.space/ via 2606:4700:20::681a:a2d (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/utkQDPP_3G

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

Checked 2026-11-11 22:09:34 UTC. Full DNS report: dns.pizza/domain/dbzgt123.space · Age, certificate and blocklists: how.is/dbzgt123.space · JSON: /api/v1/dbzgt123.space