IPv6
Measured 2026-11-13 06:07 UTC · aaaa.botThe website has no IPv6.
azbyka.ru has no IPv6 address published.
- ✗ azbyka.ru: no IPv6 address
- ✗ www.azbyka.ru: no IPv6 address
- ✓ Mail: 1 of 1 servers have IPv6
- ✓ Nameservers: 3 of 3 have IPv6
Details: published addresses and what answered
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| azbyka.ru | Publishedno IPv6 address published | Answers when we connectnothing to test |
| www.azbyka.ru | Publishedno IPv6 address published | Answers when we connectnothing to test |
Publishedmx.yandex.net | Answers when we connect✓ has IPv6 | |
| Nameservers | Publishedns.masterhost.runs2.masterhost.runs1.masterhost.ru | Answers when we connect✓ has IPv6✓ has IPv6✓ has IPv6 |
See where it lives on the IPv4 map →
Lineage
Our records: Jan 4, 2009 → Nov 14, 2026Oldest registry snapshot we hold: 2009 · 18 renewals on record · certificate history partial so far. These dates are when our records begin, not when the domain was registered.
Registrar
- Registrator-Reg-RipnFeb 2009 – Aug 2014
- Registrator-RuMar 2015 – Jan 2017
- Rd-Rulast seen Feb 2026Jul 2017 – Feb 2026
DNS provider
- etersoft.ruJan 2009 – Jun 2026
Certificates
- Let's Encryptrenews about every 4 daysAug – Nov 2026
IPv6
- IPv6no IPv6 publishedFirst measured Nov 2026
What changed (latest 8 of 20)
- IPv6 first measured: no IPv6 published on Nov 13, 2026azbyka.ru: no IPv6 published. Grade D. Measured by aaaa.bot, 2026-11-13 06:07 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- First certificate logged (Let's Encrypt) on Aug 18, 2026The earliest certificate for this name in the public Certificate Transparency logs. Logging began in 2013, so an earlier date means someone logged an older certificate later. It does not prove when HTTPS started.
- Renewed +1 year between Jan 15, 2026 and Feb 25, 2026Expiry moved from 2026-04-04 to 2027-04-04, at RD-RU.
- Renewed +1 year between Jan 8, 2025 and Feb 12, 2025Expiry moved from 2025-04-04 to 2026-04-04, at RD-RU.
- Renewed +1 year between Jan 14, 2024 and Mar 29, 2024Expiry moved from 2024-04-04 to 2025-04-04, at RD-RU.
- Renewed +1 year between Jan 22, 2023 and Mar 2, 2023Expiry moved from 2023-04-04 to 2024-04-04, at RD-RU.
- Renewed +1 year between Jan 4, 2022 and Feb 7, 2022Expiry moved from 2022-04-04 to 2023-04-04, at RD-RU.
- Renewed +1 year between Jan 28, 2021 and Mar 10, 2021Expiry moved from 2021-04-04 to 2022-04-04, at RD-RU.
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.
Registrar and renewals: 130 WHOIS/RDAP snapshots, 2009-01-04 to 2026-05-15 (ledger built 2026-09-27). Every renewal
DNS provider, WHOIS snapshots: 128 WHOIS/RDAP snapshots that listed nameservers, 2009-01-04 to 2026-06-22 (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.
Certificates: 31 logged certificates (precertificate and final counted once), read 2026-11-14, reading incomplete. A bar is the issuer that issued the most certificates in those months; Let's Encrypt renews about every 4 days (median over 25 issuance days). Public CT logging began in 2013; older certificates appear only where someone logged them later.
Want to know when azbyka.ru changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2005 — the same year as googleapis.com, youtube.com and amazonaws.com.