Yes — elifehealthcare.online has IPv6.

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

This is a saved measurement from 2026-11-02 02:38 UTC. Check elifehealthcare.online live now

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 elifehealthcare.online has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:b824:b3b2:efcf:2704:1b70 answers · 443✓ 2a02:4780:84:8075:ce14:a13e:c7e3:a4bc answers · 443	yes
www over IPv6 www.elifehealthcare.online has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:820a:5eae:3059:197:d9ef answers · 443✓ 2a02:4780:84:a223:2161:ebb0:2af7:8471 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. athena.dns-parking.com ✓apollo.dns-parking.com ✓	yes

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

https://elifehealthcare.online/ via 2a02:4780:84:b824:b3b2:efcf:2704:1b70 → 302https://elifehealthcare.online/dashboard via 2a02:4780:84:b824:b3b2:efcf:2704:1b70 → 302https://elifehealthcare.online/login via 2a02:4780:84:b824:b3b2:efcf:2704:1b70 → 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/elifehealthcare.online.svg)](https://aaaa.bot/elifehealthcare.online)

Check again

elifehealthcare.online Has IPv6

A (IPv4)	88.222.222.250 84.32.84.179
AAAA (IPv6)	2a02:4780:84:b824:b3b2:efcf:2704:1b70 2a02:4780:84:8075:ce14:a13e:c7e3:a4bc

www.elifehealthcare.online Has IPv6

Alias of	www.elifehealthcare.online.cdn.hstgr.net
A (IPv4)	88.223.87.78 147.79.72.41
AAAA (IPv6)	2a02:4780:84:820a:5eae:3059:197:d9ef 2a02:4780:84:a223:2161:ebb0:2af7:8471

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: elifehealthcare.online
Measured 2026-11-02 02:38:16 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    88.222.222.250, 84.32.84.179
AAAA (IPv6): 2a02:4780:84:b824:b3b2:efcf:2704:1b70, 2a02:4780:84:8075:ce14:a13e:c7e3:a4bc
www AAAA:    2a02:4780:84:820a:5eae:3059:197:d9ef, 2a02:4780:84:a223:2161:ebb0:2af7:8471

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: elifehealthcare.online has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:b824:b3b2:efcf:2704:1b70: answers (TCP 443)
    2a02:4780:84:8075:ce14:a13e:c7e3:a4bc: answers (TCP 443)
- www over IPv6: www.elifehealthcare.online has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:820a:5eae:3059:197:d9ef: answers (TCP 443)
    2a02:4780:84:a223:2161:ebb0:2af7:8471: 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 2 redirects: HTTP 200.
    https://elifehealthcare.online/ via 2a02:4780:84:b824:b3b2:efcf:2704:1b70 -> HTTP 302, certificate: valid
    https://elifehealthcare.online/dashboard via 2a02:4780:84:b824:b3b2:efcf:2704:1b70 -> HTTP 302, certificate: valid
    https://elifehealthcare.online/login via 2a02:4780:84:b824:b3b2:efcf:2704:1b70 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/klV8J2SR6j

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

Checked 2026-11-02 02:38:16 UTC. Full DNS report: dns.pizza/domain/elifehealthcare.online · JSON: /api/v1/elifehealthcare.online