IPv6
Measured 2026-11-15 15:47 UTC · aaaa.botThe website has no IPv6.
8888.bg has no IPv6 address published.
- ✗ 8888.bg: no IPv6 address
- ✗ www.8888.bg: no IPv6 address
- ✗ Mail: 0 of 1 servers have IPv6
- ✓ Nameservers: 4 of 4 have IPv6
Details: published addresses and what answered
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| 8888.bg | Publishedno IPv6 address published | Answers when we connectnothing to test |
| www.8888.bg | Publishedno IPv6 address published | Answers when we connectnothing to test |
Publishedmail.e-card.bg | Answers when we connect✗ no IPv6 | |
| Nameservers | Publishedns-1236.awsdns-26.orgns-1715.awsdns-22.co.ukns-325.awsdns-40.comns-709.awsdns-24.net | Answers when we connect✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6 |
See where it lives on the IPv4 map →
Lineage
Our records: May 2, 2025 → Nov 15, 2026These dates are when our records begin, not when the domain was registered.
DNS provider
- Amazon Route 53May 2025 – Jun 2026
IPv6
- IPv6no IPv6 publishedFirst measured Nov 2026
What changed
- IPv6 first measured: no IPv6 published on Nov 15, 20268888.bg: no IPv6 published. Grade D. Measured by aaaa.bot, 2026-11-15 15:47 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
Solid bar: the stretch we observed that name. Dot: a single sighting. Dotted line: no record between sightings of the same name. Nothing is drawn between different names.
DNS provider, WHOIS snapshots: 8 WHOIS/RDAP snapshots that listed nameservers, 2025-05-02 to 2026-06-30 (who.is archive). Both sources feed one row per provider (hover a bar to see which); a change is placed between the nearest observations on either side, and where the two sources disagree, both are listed under What changed.
Want to know when 8888.bg changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.