No — drgn38.buzz is IPv4 only.

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

This is a saved measurement from 2026-11-12 09:56 UTC. Check drgn38.buzz live now

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
drgn38.buzz has no AAAA record.		no
www over IPv6
www.drgn38.buzz has 2 IPv6 addresses and answers on every one we tested.
✓ 2606:4700:3037::ac43:8346 answers · 443✓ 2606:4700:3036::6815:a5f answers · 443
yes
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.
rayne.ns.cloudflare.com ✓yew.ns.cloudflare.com ✓
yes

What's keeping drgn38.buzz from an A

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

Check again

drgn38.buzz  IPv4 only

A (IPv4)89.248.67.48
AAAA (IPv6)none

www.drgn38.buzz  Has IPv6

A (IPv4)172.67.131.70
104.21.10.95
AAAA (IPv6)2606:4700:3037::ac43:8346
2606:4700:3036::6815:a5f

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

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

Checked 2026-11-12 09:56:36 UTC. Full DNS report: dns.pizza/domain/drgn38.buzz · Age, certificate and blocklists: how.is/drgn38.buzz · JSON: /api/v1/drgn38.buzz