Yes — hdking.taxi has IPv6.

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

B
IPv6 readiness
Works over IPv6, with one gap: its nameservers lack IPv6.
Website over IPv6
hdking.taxi has 4 IPv6 addresses and answers on every one we tested (4 more not tested).
✓ 2a05:d014:179b:c402:7bb:d313:bbe5:dab4 answers · 443✓ 2a05:d014:179b:c403:73e:e69:eba6:eb42 answers · 443✓ 2a05:d018:1d22:800:cf3f:4553:9200:9ed9 answers · 443✓ 2a05:d014:179b:c400:ef54:1150:2729:2038 answers · 443– 2a05:d018:1d22:801:d2f9:a416:8dd7:17c8 not tested– 2a05:d014:179b:c403:dd25:8a86:66b7:2401 not tested– 2600:1f1c:6db:8801:82d6:fcb5:2ee7:a07f not tested– 2406:da1e:214:c901:6aaa:58d0:cfa:ebce not tested
yes
www over IPv6
www.hdking.taxi has 4 IPv6 addresses and answers on every one we tested (4 more not tested).
✓ 2600:1f1c:6db:8801:82d6:fcb5:2ee7:a07f answers · 443✓ 2406:da1e:214:c901:6aaa:58d0:cfa:ebce answers · 443✓ 2a05:d014:179b:c403:73e:e69:eba6:eb42 answers · 443✓ 2a05:d014:179b:c403:dd25:8a86:66b7:2401 answers · 443– 2a05:d018:1d22:801:d2f9:a416:8dd7:17c8 not tested– 2a05:d014:179b:c400:ef54:1150:2729:2038 not tested– 2a05:d014:179b:c402:7bb:d313:bbe5:dab4 not tested– 2a05:d018:1d22:800:cf3f:4553:9200:9ed9 not tested
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
No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.
ns1.dns-redirect.com ✗ns2.dns-redirect.com ✗
no
HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 403.
https://hdking.taxi/ via 2a05:d014:179b:c402:7bb:d313:bbe5:dab4 → 301https://expireddomains.com/domain/hdking.taxi?utm_source=redi via 2606:4700:20::681a:e7a → 403
works
 Which outside scripts, fonts, payments or chat hdking.taxi loads from have no IPv6.
 Load hdking.taxi over IPv6 from up to six other places — a second opinion.

What's keeping hdking.taxi from an A

  1. Nameservers without IPv6
    ns1.dns-redirect.com, ns2.dns-redirect.com 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

hdking.taxi  Has IPv6

A (IPv4)5.78.156.59
46.62.237.138
195.201.128.179
5.161.47.86
76.223.91.20
AAAA (IPv6)2a05:d014:179b:c402:7bb:d313:bbe5:dab4
2a05:d014:179b:c403:73e:e69:eba6:eb42
2a05:d018:1d22:800:cf3f:4553:9200:9ed9
2a05:d014:179b:c400:ef54:1150:2729:2038
2a05:d018:1d22:801:d2f9:a416:8dd7:17c8
2a05:d014:179b:c403:dd25:8a86:66b7:2401
2600:1f1c:6db:8801:82d6:fcb5:2ee7:a07f
2406:da1e:214:c901:6aaa:58d0:cfa:ebce

www.hdking.taxi  Has IPv6

A (IPv4)5.78.156.59
46.62.237.138
195.201.128.179
5.161.47.86
76.223.91.20
AAAA (IPv6)2600:1f1c:6db:8801:82d6:fcb5:2ee7:a07f
2406:da1e:214:c901:6aaa:58d0:cfa:ebce
2a05:d014:179b:c403:73e:e69:eba6:eb42
2a05:d014:179b:c403:dd25:8a86:66b7:2401
2a05:d018:1d22:801:d2f9:a416:8dd7:17c8
2a05:d014:179b:c400:ef54:1150:2729:2038
2a05:d014:179b:c402:7bb:d313:bbe5:dab4
2a05:d018:1d22:800:cf3f:4553:9200:9ed9

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

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

Checked 2026-11-11 23:58:30 UTC. Full DNS report: dns.pizza/domain/hdking.taxi · Age, certificate and blocklists: how.is/hdking.taxi · JSON: /api/v1/hdking.taxi