Yes — account.weightwatchers.ca has IPv6.

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

This is a saved measurement from 2026-11-15 19:14 UTC. Check account.weightwatchers.ca live now

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 account.weightwatchers.ca has 4 IPv6 addresses and answers on every one we tested. ✓ 2a04:4e42::611 answers · 443✓ 2a04:4e42:200::611 answers · 443✓ 2a04:4e42:400::611 answers · 443✓ 2a04:4e42:600::611 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 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns-135.awsdns-16.com ✓ns-1466.awsdns-55.org ✓ns-1967.awsdns-53.co.uk ✓ns-951.awsdns-54.net ✓	yes

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

https://account.weightwatchers.ca/ via 2a04:4e42::611 → 307https://cmx.weightwatchers.ca/login?redirect_uri=https%3A%2F%2Faccount.weightwatchers.ca%2F via 2600:9000:2305:6600:15:ade3:c0c0:93a1 → 302https://auth.weightwatchers.ca/openam/oauth2/authorize?response_type=id_token&client_id=webCMX&scope=openid%20session&redirect_uri=https://cmx.weightwatchers.ca/auth&nonce=1573dc99d31effaf939414021180cf80&state=https%3A%2F%2Faccount.weightwatchers.ca%2F via 2600:9000:24f3:a000:14:bd60:d640:93a1 → 302https://auth.weightwatchers.ca/v2/login?goto=https%3A%2F%2Fauth.weightwatchers.ca%2Fopenam%2Foauth2%2Fauthorize%3Fresponse_type%3Did_token%26client_id%3DwebCMX%26scope%3Dopenid%2520session%26redirect_uri%3Dhttps%3A%2F%2Fcmx.weightwatchers.ca%2Fauth%26nonce%3D1573dc99d31effaf939414021180cf80%26state%3Dhttps%3A%2F%2Faccount.weightwatchers.ca%2F via 2600:9000:24f3:a000:14:bd60:d640:93a1 → 302https://auth.weightwatchers.ca/v2/login/?goto=https%3A%2F%2Fauth.weightwatchers.ca%2Fopenam%2Foauth2%2Fauthorize%3Fresponse_type%3Did_token%26client_id%3DwebCMX%26scope%3Dopenid%2520session%26redirect_uri%3Dhttps%3A%2F%2Fcmx.weightwatchers.ca%2Fauth%26nonce%3D1573dc99d31effaf939414021180cf80%26state%3Dhttps%3A%2F%2Faccount.weightwatchers.ca%2F via 2600:9000:24f3:a000:14:bd60:d640:93a1 → 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/account.weightwatchers.ca.svg)](https://aaaa.bot/account.weightwatchers.ca)

Check again

account.weightwatchers.ca Has IPv6

Alias of	dualstack.weightwatchers.map.fastly.net
A (IPv4)	151.101.2.99 151.101.66.99 151.101.130.99 151.101.194.99
AAAA (IPv6)	2a04:4e42::611 2a04:4e42:200::611 2a04:4e42:400::611 2a04:4e42:600::611

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: account.weightwatchers.ca
Measured 2026-11-15 19:14:49 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    151.101.2.99, 151.101.66.99, 151.101.130.99, 151.101.194.99
AAAA (IPv6): 2a04:4e42::611, 2a04:4e42:200::611, 2a04:4e42:400::611, 2a04:4e42:600::611

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: account.weightwatchers.ca has 4 IPv6 addresses and answers on every one we tested.
    2a04:4e42::611: answers (TCP 443)
    2a04:4e42:200::611: answers (TCP 443)
    2a04:4e42:400::611: answers (TCP 443)
    2a04:4e42:600::611: 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: 4 of 4 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 4 redirects: HTTP 200.
    https://account.weightwatchers.ca/ via 2a04:4e42::611 -> HTTP 307, certificate: valid
    https://cmx.weightwatchers.ca/login?redirect_uri=https%3A%2F%2Faccount.weightwatchers.ca%2F via 2600:9000:2305:6600:15:ade3:c0c0:93a1 -> HTTP 302, certificate: valid
    https://auth.weightwatchers.ca/openam/oauth2/authorize?response_type=id_token&client_id=webCMX&scope=openid%20session&redirect_uri=https://cmx.weightwatchers.ca/auth&nonce=1573dc99d31effaf939414021180cf80&state=https%3A%2F%2Faccount.weightwatchers.ca%2F via 2600:9000:24f3:a000:14:bd60:d640:93a1 -> HTTP 302, certificate: valid
    https://auth.weightwatchers.ca/v2/login?goto=https%3A%2F%2Fauth.weightwatchers.ca%2Fopenam%2Foauth2%2Fauthorize%3Fresponse_type%3Did_token%26client_id%3DwebCMX%26scope%3Dopenid%2520session%26redirect_uri%3Dhttps%3A%2F%2Fcmx.weightwatchers.ca%2Fauth%26nonce%3D1573dc99d31effaf939414021180cf80%26state%3Dhttps%3A%2F%2Faccount.weightwatchers.ca%2F via 2600:9000:24f3:a000:14:bd60:d640:93a1 -> HTTP 302, certificate: valid
    https://auth.weightwatchers.ca/v2/login/?goto=https%3A%2F%2Fauth.weightwatchers.ca%2Fopenam%2Foauth2%2Fauthorize%3Fresponse_type%3Did_token%26client_id%3DwebCMX%26scope%3Dopenid%2520session%26redirect_uri%3Dhttps%3A%2F%2Fcmx.weightwatchers.ca%2Fauth%26nonce%3D1573dc99d31effaf939414021180cf80%26state%3Dhttps%3A%2F%2Faccount.weightwatchers.ca%2F via 2600:9000:24f3:a000:14:bd60:d640:93a1 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/TC6V0NyMWH

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

Checked 2026-11-15 19:14:49 UTC. Full DNS report: dns.pizza/domain/account.weightwatchers.ca · Age, certificate and blocklists: how.is/account.weightwatchers.ca · JSON: /api/v1/account.weightwatchers.ca