Yes — dailybeacon.blog has IPv6.

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

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 dailybeacon.blog has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:e21:bbb4:2017:8cd5:3f16 answers · 443✓ 2a02:4780:84:2c6b:1b51:13a5:b9fa:7d0e answers · 443	yes
www over IPv6 www.dailybeacon.blog has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:21:a9a2:61c6:e105:6a5b:f495 answers · 443✓ 2a02:4780:1d:f329:97a3:6a19:7c62:4ca0 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: HTTP 200.

https://dailybeacon.blog/ via 2a02:4780:84:e21:bbb4:2017:8cd5:3f16 → 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/dailybeacon.blog.svg)](https://aaaa.bot/dailybeacon.blog)

Check again

dailybeacon.blog Has IPv6

A (IPv4)	88.222.222.204 84.32.84.81
AAAA (IPv6)	2a02:4780:84:e21:bbb4:2017:8cd5:3f16 2a02:4780:84:2c6b:1b51:13a5:b9fa:7d0e

www.dailybeacon.blog Has IPv6

Alias of	www.dailybeacon.blog.cdn.hstgr.net
A (IPv4)	84.32.84.27 88.222.222.171
AAAA (IPv6)	2a02:4780:21:a9a2:61c6:e105:6a5b:f495 2a02:4780:1d:f329:97a3:6a19:7c62:4ca0

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: dailybeacon.blog
Measured 2026-11-03 23:43:06 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    88.222.222.204, 84.32.84.81
AAAA (IPv6): 2a02:4780:84:e21:bbb4:2017:8cd5:3f16, 2a02:4780:84:2c6b:1b51:13a5:b9fa:7d0e
www AAAA:    2a02:4780:21:a9a2:61c6:e105:6a5b:f495, 2a02:4780:1d:f329:97a3:6a19:7c62:4ca0

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: dailybeacon.blog has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:e21:bbb4:2017:8cd5:3f16: answers (TCP 443)
    2a02:4780:84:2c6b:1b51:13a5:b9fa:7d0e: answers (TCP 443)
- www over IPv6: www.dailybeacon.blog has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:21:a9a2:61c6:e105:6a5b:f495: answers (TCP 443)
    2a02:4780:1d:f329:97a3:6a19:7c62:4ca0: 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: HTTP 200.
    https://dailybeacon.blog/ via 2a02:4780:84:e21:bbb4:2017:8cd5:3f16 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/JAtxu1LxH_

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

Checked 2026-11-03 23:43:06 UTC. Full DNS report: dns.pizza/domain/dailybeacon.blog · Age, certificate and blocklists: how.is/dailybeacon.blog · JSON: /api/v1/dailybeacon.blog