Yes — meetpatientrewards.com has IPv6.

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

This is a saved measurement from 2026-11-07 05:34 UTC. Check meetpatientrewards.com live now

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 meetpatientrewards.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3037::ac43:8d05 answers · 443✓ 2606:4700:3031::6815:36b4 answers · 443	yes
www over IPv6 www.meetpatientrewards.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3031::6815:36b4 answers · 443✓ 2606:4700:3037::ac43:8d05 answers · 443	yes
Mail servers (MX) have IPv6 Every mail server has an AAAA record. aspmx.l.google.com ✓alt3.aspmx.l.google.com ✓alt4.aspmx.l.google.com ✓alt1.aspmx.l.google.com ✓alt2.aspmx.l.google.com ✓	yes
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. jaziel.ns.cloudflare.com ✓monroe.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Redirects to patientrewards.app, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.

https://meetpatientrewards.com/ via 2606:4700:3037::ac43:8d05 → 301https://patientrewards.app/ · redirects to patientrewards.app, which has no IPv6 address

problem

Nothing keeping you from an A

A redirect leads off IPv6
Redirects to patientrewards.app, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all. Give the redirect target IPv6 too, or redirect somewhere that has it.

Check again

meetpatientrewards.com Has IPv6

A (IPv4)	104.21.54.180 172.67.141.5
AAAA (IPv6)	2606:4700:3037::ac43:8d05 2606:4700:3031::6815:36b4

www.meetpatientrewards.com Has IPv6

A (IPv4)	104.21.54.180 172.67.141.5
AAAA (IPv6)	2606:4700:3031::6815:36b4 2606:4700:3037::ac43:8d05

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: meetpatientrewards.com
Measured 2026-11-07 05:34:01 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.54.180, 172.67.141.5
AAAA (IPv6): 2606:4700:3037::ac43:8d05, 2606:4700:3031::6815:36b4
www AAAA:    2606:4700:3031::6815:36b4, 2606:4700:3037::ac43:8d05

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: meetpatientrewards.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3037::ac43:8d05: answers (TCP 443)
    2606:4700:3031::6815:36b4: answers (TCP 443)
- www over IPv6: www.meetpatientrewards.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3031::6815:36b4: answers (TCP 443)
    2606:4700:3037::ac43:8d05: answers (TCP 443)
- Mail servers (MX) have IPv6: Every mail server 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): Redirects to patientrewards.app, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.
    https://meetpatientrewards.com/ via 2606:4700:3037::ac43:8d05 -> HTTP 301, certificate: valid
    https://patientrewards.app/ (redirects to patientrewards.app, which has no IPv6 address)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/jspeSwB-hx

Permanent link: aaaa.bot/r/jspeSwB-hx · How we measure

Checked 2026-11-07 05:34:01 UTC. Full DNS report: dns.pizza/domain/meetpatientrewards.com · Age, certificate and blocklists: how.is/meetpatientrewards.com · JSON: /api/v1/meetpatientrewards.com