Yes — m.8888.bg has IPv6.

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

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 m.8888.bg has 4 IPv6 addresses and answers on every one we tested (4 more not tested). ✓ 2600:9000:250a:7800:0:a4f9:1380:93a1 answers · 443✓ 2600:9000:250a:1400:0:a4f9:1380:93a1 answers · 443✓ 2600:9000:250a:8800:0:a4f9:1380:93a1 answers · 443✓ 2600:9000:250a:8000:0:a4f9:1380:93a1 answers · 443– 2600:9000:250a:b000:0:a4f9:1380:93a1 not tested– 2600:9000:250a:c600:0:a4f9:1380:93a1 not tested– 2600:9000:250a:8600:0:a4f9:1380:93a1 not tested– 2600:9000:250a:2200:0:a4f9:1380:93a1 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 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns-1236.awsdns-26.org ✓ns-1715.awsdns-22.co.uk ✓ns-325.awsdns-40.com ✓ns-709.awsdns-24.net ✓	yes

HTTPS over IPv6 · not part of the grade yet
m.8888.bg didn't complete an HTTPS request over IPv6 (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE).

https://m.8888.bg/ via 2600:9000:250a:7800:0:a4f9:1380:93a1 · ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE

Nothing keeping you from an A

Nothing to fix
Show it off: add the badge to your README.
[![IPv6](https://aaaa.bot/badge/m.8888.bg.svg)](https://aaaa.bot/m.8888.bg)

Check again

m.8888.bg Has IPv6

Alias of	app75.affiliateservers.com → d1xsifs4eoub7y.cloudfront.net
A (IPv4)	18.160.10.22 18.160.10.109 18.160.10.6 18.160.10.111
AAAA (IPv6)	2600:9000:250a:7800:0:a4f9:1380:93a1 2600:9000:250a:1400:0:a4f9:1380:93a1 2600:9000:250a:8800:0:a4f9:1380:93a1 2600:9000:250a:8000:0:a4f9:1380:93a1 2600:9000:250a:b000:0:a4f9:1380:93a1 2600:9000:250a:c600:0:a4f9:1380:93a1 2600:9000:250a:8600:0:a4f9:1380:93a1 2600:9000:250a:2200:0:a4f9:1380:93a1

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: m.8888.bg
Measured 2026-11-15 17:08:59 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    18.160.10.22, 18.160.10.109, 18.160.10.6, 18.160.10.111
AAAA (IPv6): 2600:9000:250a:7800:0:a4f9:1380:93a1, 2600:9000:250a:1400:0:a4f9:1380:93a1, 2600:9000:250a:8800:0:a4f9:1380:93a1, 2600:9000:250a:8000:0:a4f9:1380:93a1, 2600:9000:250a:b000:0:a4f9:1380:93a1, 2600:9000:250a:c600:0:a4f9:1380:93a1, 2600:9000:250a:8600:0:a4f9:1380:93a1, 2600:9000:250a:2200:0:a4f9:1380:93a1

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: m.8888.bg has 4 IPv6 addresses and answers on every one we tested (4 more not tested).
    2600:9000:250a:7800:0:a4f9:1380:93a1: answers (TCP 443)
    2600:9000:250a:1400:0:a4f9:1380:93a1: answers (TCP 443)
    2600:9000:250a:8800:0:a4f9:1380:93a1: answers (TCP 443)
    2600:9000:250a:8000:0:a4f9:1380:93a1: answers (TCP 443)
    2600:9000:250a:b000:0:a4f9:1380:93a1: not tested
    2600:9000:250a:c600:0:a4f9:1380:93a1: not tested
    2600:9000:250a:8600:0:a4f9:1380:93a1: not tested
    2600:9000:250a:2200:0:a4f9:1380:93a1: not tested
- 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): m.8888.bg didn't complete an HTTPS request over IPv6 (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE).
    https://m.8888.bg/ via 2600:9000:250a:7800:0:a4f9:1380:93a1 (ERR_SSL_SSL/TLS_ALERT_HANDSHAKE_FAILURE)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/CY4WVuddEz

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

Checked 2026-11-15 17:08:59 UTC. Full DNS report: dns.pizza/domain/m.8888.bg · Age, certificate and blocklists: how.is/m.8888.bg · JSON: /api/v1/m.8888.bg