Yes — ssl-mobile.com has IPv6.

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

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 ssl-mobile.com has an AAAA record and answers on it. ✓ 2a02:4780:75:a366::1 answers · 443	yes
www over IPv6 www.ssl-mobile.com has an AAAA record and answers on it. ✓ 2a02:4780:75:a366::1 answers · 443	yes
Mail servers (MX) have IPv6 Every mail server has an AAAA record. mx1.hostinger.com ✓mx2.hostinger.com ✓	yes
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. nebula.dns-parking.com ✓aurora.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://ssl-mobile.com/ via 2a02:4780:75:a366::1 → 302https://auth.ssl-mobile.com/application/o/authorize/?client_id=W1BiFMYyyEqqSlMsMkSPAB4JmIOsMoPcLczS0gWN&redirect_uri=https%3A%2F%2Fssl-mobile.com%2Foutpost.goauthentik.io%2Fcallback%3FX-authentik-auth-callback%3Dtrue&response_type=code&scope=entitlements+email+ak_proxy+profile+openid&state=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnb2F1dGhlbnRpay5pby9vdXRwb3N0L1cxQmlGTVl5eUVxcVNsTXNNa1NQQUI0Sm1JT3NNb1BjTGN6UzBnV04iLCJzaWQiOiJjNTI0ZGEzYi05NWZhLTRlOGQtYTBhZi1jMjI1YmUwMjJjOGYiLCJzdGF0ZSI6IjVhMGIwZGMwLWI2NGEtNDQ4Mi04MDM4LTFmZjAzYmRiMmVhYSIsInJlZGlyZWN0IjoiaHR0cHM6Ly9zc2wtbW9iaWxlLmNvbS8ifQ.Yu6n9ZZ9urdc_hqHfT1YcV0wxVe2RoAdHF6QaVe08oQ via 2a02:4780:75:a366::1 → 302https://auth.ssl-mobile.com/if/flow/ssl-mobile-authentication-flow/?client_id=W1BiFMYyyEqqSlMsMkSPAB4JmIOsMoPcLczS0gWN&redirect_uri=https%3A%2F%2Fssl-mobile.com%2Foutpost.goauthentik.io%2Fcallback%3FX-authentik-auth-callback%3Dtrue&response_type=code&scope=entitlements+email+ak_proxy+profile+openid&state=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnb2F1dGhlbnRpay5pby9vdXRwb3N0L1cxQmlGTVl5eUVxcVNsTXNNa1NQQUI0Sm1JT3NNb1BjTGN6UzBnV04iLCJzaWQiOiJjNTI0ZGEzYi05NWZhLTRlOGQtYTBhZi1jMjI1YmUwMjJjOGYiLCJzdGF0ZSI6IjVhMGIwZGMwLWI2NGEtNDQ4Mi04MDM4LTFmZjAzYmRiMmVhYSIsInJlZGlyZWN0IjoiaHR0cHM6Ly9zc2wtbW9iaWxlLmNvbS8ifQ.Yu6n9ZZ9urdc_hqHfT1YcV0wxVe2RoAdHF6QaVe08oQ&next=%2Fapplication%2Fo%2Fauthorize%2F%3Fclient_id%3DW1BiFMYyyEqqSlMsMkSPAB4JmIOsMoPcLczS0gWN%26redirect_uri%3Dhttps%253A%252F%252Fssl-mobile.com%252Foutpost.goauthentik.io%252Fcallback%253FX-authentik-auth-callback%253Dtrue%26response_type%3Dcode%26scope%3Dentitlements%2Bemail%2Bak_proxy%2Bprofile%2Bopenid%26state%3DeyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnb2F1dGhlbnRpay5pby9vdXRwb3N0L1cxQmlGTVl5eUVxcVNsTXNNa1NQQUI0Sm1JT3NNb1BjTGN6UzBnV04iLCJzaWQiOiJjNTI0ZGEzYi05NWZhLTRlOGQtYTBhZi1jMjI1YmUwMjJjOGYiLCJzdGF0ZSI6IjVhMGIwZGMwLWI2NGEtNDQ4Mi04MDM4LTFmZjAzYmRiMmVhYSIsInJlZGlyZWN0IjoiaHR0cHM6Ly9zc2wtbW9iaWxlLmNvbS8ifQ.Yu6n9ZZ9urdc_hqHfT1YcV0wxVe2RoAdHF6QaVe08oQ via 2a02:4780:75:a366::1 → 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/ssl-mobile.com.svg)](https://aaaa.bot/ssl-mobile.com)

Check again

ssl-mobile.com Has IPv6

A (IPv4)	2.25.71.197
AAAA (IPv6)	2a02:4780:75:a366::1

www.ssl-mobile.com Has IPv6

Alias of	ssl-mobile.com
A (IPv4)	2.25.71.197
AAAA (IPv6)	2a02:4780:75:a366::1

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: ssl-mobile.com
Measured 2026-11-11 05:43:36 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    2.25.71.197
AAAA (IPv6): 2a02:4780:75:a366::1
www AAAA:    2a02:4780:75:a366::1

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: ssl-mobile.com has an AAAA record and answers on it.
    2a02:4780:75:a366::1: answers (TCP 443)
- www over IPv6: www.ssl-mobile.com has an AAAA record and answers on it.
    2a02:4780:75:a366::1: 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): Loads over IPv6 with a valid certificate after 2 redirects: HTTP 200.
    https://ssl-mobile.com/ via 2a02:4780:75:a366::1 -> HTTP 302, certificate: valid
    https://auth.ssl-mobile.com/application/o/authorize/?client_id=W1BiFMYyyEqqSlMsMkSPAB4JmIOsMoPcLczS0gWN&redirect_uri=https%3A%2F%2Fssl-mobile.com%2Foutpost.goauthentik.io%2Fcallback%3FX-authentik-auth-callback%3Dtrue&response_type=code&scope=entitlements+email+ak_proxy+profile+openid&state=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnb2F1dGhlbnRpay5pby9vdXRwb3N0L1cxQmlGTVl5eUVxcVNsTXNNa1NQQUI0Sm1JT3NNb1BjTGN6UzBnV04iLCJzaWQiOiJjNTI0ZGEzYi05NWZhLTRlOGQtYTBhZi1jMjI1YmUwMjJjOGYiLCJzdGF0ZSI6IjVhMGIwZGMwLWI2NGEtNDQ4Mi04MDM4LTFmZjAzYmRiMmVhYSIsInJlZGlyZWN0IjoiaHR0cHM6Ly9zc2wtbW9iaWxlLmNvbS8ifQ.Yu6n9ZZ9urdc_hqHfT1YcV0wxVe2RoAdHF6QaVe08oQ via 2a02:4780:75:a366::1 -> HTTP 302, certificate: valid
    https://auth.ssl-mobile.com/if/flow/ssl-mobile-authentication-flow/?client_id=W1BiFMYyyEqqSlMsMkSPAB4JmIOsMoPcLczS0gWN&redirect_uri=https%3A%2F%2Fssl-mobile.com%2Foutpost.goauthentik.io%2Fcallback%3FX-authentik-auth-callback%3Dtrue&response_type=code&scope=entitlements+email+ak_proxy+profile+openid&state=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnb2F1dGhlbnRpay5pby9vdXRwb3N0L1cxQmlGTVl5eUVxcVNsTXNNa1NQQUI0Sm1JT3NNb1BjTGN6UzBnV04iLCJzaWQiOiJjNTI0ZGEzYi05NWZhLTRlOGQtYTBhZi1jMjI1YmUwMjJjOGYiLCJzdGF0ZSI6IjVhMGIwZGMwLWI2NGEtNDQ4Mi04MDM4LTFmZjAzYmRiMmVhYSIsInJlZGlyZWN0IjoiaHR0cHM6Ly9zc2wtbW9iaWxlLmNvbS8ifQ.Yu6n9ZZ9urdc_hqHfT1YcV0wxVe2RoAdHF6QaVe08oQ&next=%2Fapplication%2Fo%2Fauthorize%2F%3Fclient_id%3DW1BiFMYyyEqqSlMsMkSPAB4JmIOsMoPcLczS0gWN%26redirect_uri%3Dhttps%253A%252F%252Fssl-mobile.com%252Foutpost.goauthentik.io%252Fcallback%253FX-authentik-auth-callback%253Dtrue%26response_type%3Dcode%26scope%3Dentitlements%2Bemail%2Bak_proxy%2Bprofile%2Bopenid%26state%3DeyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnb2F1dGhlbnRpay5pby9vdXRwb3N0L1cxQmlGTVl5eUVxcVNsTXNNa1NQQUI0Sm1JT3NNb1BjTGN6UzBnV04iLCJzaWQiOiJjNTI0ZGEzYi05NWZhLTRlOGQtYTBhZi1jMjI1YmUwMjJjOGYiLCJzdGF0ZSI6IjVhMGIwZGMwLWI2NGEtNDQ4Mi04MDM4LTFmZjAzYmRiMmVhYSIsInJlZGlyZWN0IjoiaHR0cHM6Ly9zc2wtbW9iaWxlLmNvbS8ifQ.Yu6n9ZZ9urdc_hqHfT1YcV0wxVe2RoAdHF6QaVe08oQ via 2a02:4780:75:a366::1 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/zg0UJbhfW4

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

Checked 2026-11-11 05:43:36 UTC. Full DNS report: dns.pizza/domain/ssl-mobile.com · Age, certificate and blocklists: how.is/ssl-mobile.com · JSON: /api/v1/ssl-mobile.com