Yes — prayercalendar.app has IPv6.

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

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 prayercalendar.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2600:1f18:16e:df01::258 answers · 443✓ 2600:1f18:16e:df01::259 answers · 443	yes
www over IPv6 www.prayercalendar.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2600:1f18:16e:df01::259 answers · 443✓ 2600:1f18:16e:df01::258 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. amanda.ns.cloudflare.com ✓augustus.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate: HTTP 200.

https://prayercalendar.app/ via 2600:1f18:16e:df01::258 → 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/prayercalendar.app.svg)](https://aaaa.bot/prayercalendar.app)

Check again

prayercalendar.app Has IPv6

A (IPv4)	98.84.224.111 18.208.88.157
AAAA (IPv6)	2600:1f18:16e:df01::258 2600:1f18:16e:df01::259

www.prayercalendar.app Has IPv6

Alias of	effortless-travesseiro-cca9f1.netlify.app
A (IPv4)	18.208.88.157 98.84.224.111
AAAA (IPv6)	2600:1f18:16e:df01::259 2600:1f18:16e:df01::258

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: prayercalendar.app
Measured 2026-11-03 14:25:19 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    98.84.224.111, 18.208.88.157
AAAA (IPv6): 2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259
www AAAA:    2600:1f18:16e:df01::259, 2600:1f18:16e:df01::258

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: prayercalendar.app has 2 IPv6 addresses and answers on every one we tested.
    2600:1f18:16e:df01::258: answers (TCP 443)
    2600:1f18:16e:df01::259: answers (TCP 443)
- www over IPv6: www.prayercalendar.app has 2 IPv6 addresses and answers on every one we tested.
    2600:1f18:16e:df01::259: answers (TCP 443)
    2600:1f18:16e:df01::258: 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://prayercalendar.app/ via 2600:1f18:16e:df01::258 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/qzJWPbUiDf

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

Checked 2026-11-03 14:25:19 UTC. Full DNS report: dns.pizza/domain/prayercalendar.app · Age, certificate and blocklists: how.is/prayercalendar.app · JSON: /api/v1/prayercalendar.app