Yes — mealgarden.site has IPv6.

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

IPv6 readiness

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

Website over IPv6 mealgarden.site has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3032::6815:446a answers · 443✓ 2606:4700:3037::ac43:c247 answers · 443	yes
www over IPv6 www.mealgarden.site has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3032::6815:446a answers · 443✓ 2606:4700:3037::ac43:c247 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. ophelia.ns.cloudflare.com ✓ryan.ns.cloudflare.com ✓	yes

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

https://mealgarden.site/ via 2606:4700:3032::6815:446a → 200

works

What's keeping mealgarden.site 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

mealgarden.site Has IPv6

A (IPv4)	172.67.194.71 104.21.68.106
AAAA (IPv6)	2606:4700:3032::6815:446a 2606:4700:3037::ac43:c247

www.mealgarden.site Has IPv6

A (IPv4)	172.67.194.71 104.21.68.106
AAAA (IPv6)	2606:4700:3032::6815:446a 2606:4700:3037::ac43:c247

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: mealgarden.site
Measured 2026-11-12 13:49:24 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    172.67.194.71, 104.21.68.106
AAAA (IPv6): 2606:4700:3032::6815:446a, 2606:4700:3037::ac43:c247
www AAAA:    2606:4700:3032::6815:446a, 2606:4700:3037::ac43:c247

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: mealgarden.site has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3032::6815:446a: answers (TCP 443)
    2606:4700:3037::ac43:c247: answers (TCP 443)
- www over IPv6: www.mealgarden.site has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3032::6815:446a: answers (TCP 443)
    2606:4700:3037::ac43:c247: 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): Loads over IPv6 with a valid certificate: HTTP 200.
    https://mealgarden.site/ via 2606:4700:3032::6815:446a -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/tPg67A-G0g

Permanent link: aaaa.bot/r/tPg67A-G0g · How we measure

Checked 2026-11-12 13:49:24 UTC. Full DNS report: dns.pizza/domain/mealgarden.site · Age, certificate and blocklists: how.is/mealgarden.site · JSON: /api/v1/mealgarden.site