Yes — jbservices.group has IPv6.

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

IPv6 readiness

Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.

Website over IPv6 jbservices.group has an AAAA record and answers on it. ✓ 2001:41d0:301::29 answers · 443	yes
www over IPv6 www.jbservices.group has an AAAA record and answers on it. ✓ 2001:41d0:301::29 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mx1.mail.ovh.net ✗mx2.mail.ovh.net ✗mx3.mail.ovh.net ✗	no
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns200.anycast.me ✗dns200.anycast.me ✗	no

HTTPS over IPv6 · not part of the grade yet
The certificate served over IPv6 at 2001:41d0:301::29 isn't valid for jbservices.group: ERR_TLS_CERT_ALTNAME_INVALID.

https://jbservices.group/ via 2001:41d0:301::29 · ERR_TLS_CERT_ALTNAME_INVALID

problem

What's keeping jbservices.group from an A

The certificate served over IPv6 is wrong
The certificate served over IPv6 at 2001:41d0:301::29 isn't valid for jbservices.group: ERR_TLS_CERT_ALTNAME_INVALID. Often the IPv6 address points at a different server (or an old one) than IPv4 does. Make sure 2001:41d0:301::29 serves the same certificate as your IPv4 address.
Mail servers without IPv6
mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net 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.
Nameservers without IPv6
ns200.anycast.me, dns200.anycast.me all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

jbservices.group Has IPv6

A (IPv4)	51.91.236.255
AAAA (IPv6)	2001:41d0:301::29

www.jbservices.group Has IPv6

A (IPv4)	51.91.236.255
AAAA (IPv6)	2001:41d0:301::29

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: jbservices.group
Measured 2026-11-05 18:59:57 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    51.91.236.255
AAAA (IPv6): 2001:41d0:301::29
www AAAA:    2001:41d0:301::29

Readiness grade C: Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.
- Website over IPv6: jbservices.group has an AAAA record and answers on it.
    2001:41d0:301::29: answers (TCP 443)
- www over IPv6: www.jbservices.group has an AAAA record and answers on it.
    2001:41d0:301::29: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers has an AAAA record.
- Nameservers have IPv6: No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): The certificate served over IPv6 at 2001:41d0:301::29 isn't valid for jbservices.group: ERR_TLS_CERT_ALTNAME_INVALID.
    https://jbservices.group/ via 2001:41d0:301::29, certificate: ERR_TLS_CERT_ALTNAME_INVALID
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/s8sulIuDd1

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

Checked 2026-11-05 18:59:57 UTC. Full DNS report: dns.pizza/domain/jbservices.group · Age, certificate and blocklists: how.is/jbservices.group · JSON: /api/v1/jbservices.group