Yes — sfterminal.online has IPv6.

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

This is a saved measurement from 2026-11-02 01:42 UTC. Check sfterminal.online live now

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 sfterminal.online has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:84:1e59:9028:c179:62cb:eb0d answers · 443✓ 2a02:4780:84:e940:df03:16e5:1f0:4725 answers · 443	yes
www over IPv6 www.sfterminal.online has 2 IPv6 addresses and answers on every one we tested. ✓ 2a02:4780:4c:b0b4:b53:79fe:1802:4dcc answers · 443✓ 2a02:4780:4d:7e25:d57d:4a59:a40e:9fad 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 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. horizon.dns-parking.com ✓orbit.dns-parking.com ✓	yes

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

https://sfterminal.online/ via 2a02:4780:84:1e59:9028:c179:62cb:eb0d → 302https://sfterminal.online/login.php via 2a02:4780:84:1e59:9028:c179:62cb:eb0d → 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/sfterminal.online.svg)](https://aaaa.bot/sfterminal.online)

Check again

sfterminal.online Has IPv6

A (IPv4)	2.57.91.133 84.32.84.174
AAAA (IPv6)	2a02:4780:84:1e59:9028:c179:62cb:eb0d 2a02:4780:84:e940:df03:16e5:1f0:4725

www.sfterminal.online Has IPv6

Alias of	www.sfterminal.online.cdn.hstgr.net
A (IPv4)	2.57.91.212 88.222.222.129
AAAA (IPv6)	2a02:4780:4c:b0b4:b53:79fe:1802:4dcc 2a02:4780:4d:7e25:d57d:4a59:a40e:9fad

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: sfterminal.online
Measured 2026-11-02 01:42:33 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    2.57.91.133, 84.32.84.174
AAAA (IPv6): 2a02:4780:84:1e59:9028:c179:62cb:eb0d, 2a02:4780:84:e940:df03:16e5:1f0:4725
www AAAA:    2a02:4780:4c:b0b4:b53:79fe:1802:4dcc, 2a02:4780:4d:7e25:d57d:4a59:a40e:9fad

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: sfterminal.online has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:84:1e59:9028:c179:62cb:eb0d: answers (TCP 443)
    2a02:4780:84:e940:df03:16e5:1f0:4725: answers (TCP 443)
- www over IPv6: www.sfterminal.online has 2 IPv6 addresses and answers on every one we tested.
    2a02:4780:4c:b0b4:b53:79fe:1802:4dcc: answers (TCP 443)
    2a02:4780:4d:7e25:d57d:4a59:a40e:9fad: 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: 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 1 redirect: HTTP 200.
    https://sfterminal.online/ via 2a02:4780:84:1e59:9028:c179:62cb:eb0d -> HTTP 302, certificate: valid
    https://sfterminal.online/login.php via 2a02:4780:84:1e59:9028:c179:62cb:eb0d -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/Wku8mb8yho

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

Checked 2026-11-02 01:42:33 UTC. Full DNS report: dns.pizza/domain/sfterminal.online · JSON: /api/v1/sfterminal.online