Yes — holycards.app has IPv6.

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

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 holycards.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:9513:8e3a:a786:876c:dcc1 answers · 443✓ 2a02:4780:84:3b86:10ed:5685:29eb:1555 answers · 443	yes
www over IPv6 www.holycards.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:6de6:c704:cc4c:365e:ae79 answers · 443✓ 2a02:4780:84:caf7:5bbe:7745:d2a5:a404 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. artemis.dns-parking.com ✓hermes.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://holycards.app/ via 2a02:4780:84:9513:8e3a:a786:876c:dcc1 → 302https://holycards.app/signin.php via 2a02:4780:84:9513:8e3a:a786:876c:dcc1 → 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/holycards.app.svg)](https://aaaa.bot/holycards.app)

Check again

holycards.app Has IPv6

A (IPv4)	84.32.84.215 2.57.91.76
AAAA (IPv6)	2a02:4780:84:9513:8e3a:a786:876c:dcc1 2a02:4780:84:3b86:10ed:5685:29eb:1555

www.holycards.app Has IPv6

Alias of	www.holycards.app.cdn.hstgr.net
A (IPv4)	84.32.84.218 88.222.222.181
AAAA (IPv6)	2a02:4780:84:6de6:c704:cc4c:365e:ae79 2a02:4780:84:caf7:5bbe:7745:d2a5:a404

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: holycards.app
Measured 2026-11-11 10:32:09 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    84.32.84.215, 2.57.91.76
AAAA (IPv6): 2a02:4780:84:9513:8e3a:a786:876c:dcc1, 2a02:4780:84:3b86:10ed:5685:29eb:1555
www AAAA:    2a02:4780:84:6de6:c704:cc4c:365e:ae79, 2a02:4780:84:caf7:5bbe:7745:d2a5:a404

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: holycards.app has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:9513:8e3a:a786:876c:dcc1: answers (TCP 443)
    2a02:4780:84:3b86:10ed:5685:29eb:1555: answers (TCP 443)
- www over IPv6: www.holycards.app has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:6de6:c704:cc4c:365e:ae79: answers (TCP 443)
    2a02:4780:84:caf7:5bbe:7745:d2a5:a404: 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://holycards.app/ via 2a02:4780:84:9513:8e3a:a786:876c:dcc1 -> HTTP 302, certificate: valid
    https://holycards.app/signin.php via 2a02:4780:84:9513:8e3a:a786:876c:dcc1 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/ePNM9laUbJ

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

Checked 2026-11-11 10:32:09 UTC. Full DNS report: dns.pizza/domain/holycards.app · Age, certificate and blocklists: how.is/holycards.app · JSON: /api/v1/holycards.app