Yes — bedger.app has IPv6.

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

This is a saved measurement from 2026-11-14 00:58 UTC. Check bedger.app live now

IPv6 readiness

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

Website over IPv6 bedger.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3036::ac43:d460 answers · 443✓ 2606:4700:3032::6815:3b26 answers · 443	yes
www over IPv6 www.bedger.app has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3032::6815:3b26 answers · 443✓ 2606:4700:3036::ac43:d460 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. maxim.ns.cloudflare.com ✓vida.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
bedger.app didn't complete an HTTPS request over IPv6 (timed out).

https://bedger.app/ via 2606:4700:3036::ac43:d460 · timed out

What's keeping bedger.app 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

bedger.app Has IPv6

A (IPv4)	104.21.59.38 172.67.212.96
AAAA (IPv6)	2606:4700:3036::ac43:d460 2606:4700:3032::6815:3b26

www.bedger.app Has IPv6

A (IPv4)	172.67.212.96 104.21.59.38
AAAA (IPv6)	2606:4700:3032::6815:3b26 2606:4700:3036::ac43:d460

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: bedger.app
Measured 2026-11-14 00:58:45 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.59.38, 172.67.212.96
AAAA (IPv6): 2606:4700:3036::ac43:d460, 2606:4700:3032::6815:3b26
www AAAA:    2606:4700:3032::6815:3b26, 2606:4700:3036::ac43:d460

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: bedger.app has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3036::ac43:d460: answers (TCP 443)
    2606:4700:3032::6815:3b26: answers (TCP 443)
- www over IPv6: www.bedger.app has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3032::6815:3b26: answers (TCP 443)
    2606:4700:3036::ac43:d460: 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): bedger.app didn't complete an HTTPS request over IPv6 (timed out).
    https://bedger.app/ via 2606:4700:3036::ac43:d460, certificate: valid (timed out)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/7uevpVjCEK

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

Checked 2026-11-14 00:58:45 UTC. Full DNS report: dns.pizza/domain/bedger.app · Age, certificate and blocklists: how.is/bedger.app · JSON: /api/v1/bedger.app