ah33.ru - robtex.com
ah33.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 195.24.68.11🇷🇺 RU-CENTER195.24.68.0/23 Route | ||||||
| PTR | wcarp.hosting.nic.ru | ||||||
| NS | ns1.r01.ru ⭐ | ||||||
| A | 31.177.80.41🇷🇺 RU-CENTER31.177.80.0/24 -NETWORK | ||||||
| PTR | ns1.r01.ru | ||||||
| NS | ns2.r01.ru | ||||||
| A | 31.177.76.41🇷🇺 RU-CENTER31.177.76.0/24 RU-SERVICE-NETWORK | ||||||
| PTR | ns2.r01.ru | ||||||
| MX | mx.yandex.net ⭐ | ||||||
| A | 2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| TXT | _globalsign-domain-verification=D08yDgz2e45-AwdxPugxJY85BIl1(0x536558)b-YLOyt1y9R | ||||||
| TXT | v=spf1 redirect=_spf.yandex.net | ||||||
| SOA | ns1.r01.rusupport@r01.ru 2025-11-26 #0 | ||||||
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4068496 | ||||||
Same first word
DNS History
12 records (4 active, 8 former)
●NSns1.r01.ru2016-03-08 → 2026-04-13 · 3 obs
● 2016-03-08 09:07:10
● 2026-04-13 06:29:50
○NSns1.teleline.ru2015-07-22 → 2015-12-02 · 4 obs
● 2015-12-02 06:13:40
○ 2016-03-08 09:07:10
○ 2026-04-13 06:29:50
●NSns2.r01.ru2016-03-08 → 2026-04-13 · 3 obs
● 2016-03-08 09:07:10
● 2026-04-13 06:29:50
○NSns3.teleline.ru2015-07-22 → 2015-12-02 · 4 obs
● 2015-12-02 06:13:40
○ 2016-03-08 09:07:10
○ 2026-04-13 06:29:50
○NSns4.teleline.ru2015-07-22 → 2015-12-02 · 4 obs
● 2015-12-02 06:13:40
○ 2016-03-08 09:07:10
○ 2026-04-13 06:29:50
○MXmail.ah33.ru2015-07-22 → 2015-12-02 · 4 obs
● 2015-12-02 06:13:40
○ 2016-03-08 09:07:10
○ 2026-04-13 06:29:50
●MXmx.yandex.net2021-02-28 → 2026-04-13 · 3 obs
● 2021-02-28 13:54:20
● 2026-04-13 06:29:50
○A176.112.199.1652017-02-17 → 2017-02-17 · 4 obs
● 2017-02-17 00:22:10
○ 2021-02-28 13:54:20
○ 2026-04-13 06:29:50
○A176.112.202.462016-03-08 → 2016-03-08 · 4 obs
● 2016-03-08 09:07:10
○ 2016-06-22 05:08:18
○ 2026-04-13 06:29:50
●A195.24.68.112021-02-28 → 2026-04-13 · 3 obs
● 2021-02-28 13:54:20
● 2026-04-13 06:29:50
○A77.246.158.2332016-06-22 → 2016-06-22 · 4 obs
● 2016-06-22 05:08:18
○ 2017-02-17 00:22:10
○ 2026-04-13 06:29:50
○A93.189.248.172015-07-22 → 2015-12-02 · 4 obs
● 2015-12-02 06:13:40
○ 2016-03-08 09:07:10
○ 2026-04-13 06:29:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net... | - |
| ah33.ru | ns1.r01.ru, ns2.r01.ru | 2 records |
✅ Authoritative Response
Server:31.177.76.41
NS records: ns1.r01.ru, ns2.r01.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ah33.ru (unsigned zone)
⏱️ Timing
Total: 980ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 195.24.68.11 |
| NS | 2 | ns2.r01.ru, ns1.r01.ru |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 2 | v=spf1 redirect=_spf.yandex.net, _globalsign-domain-verification=D08yDgz2 |
| SOA | 1 | ns1.r01.ru support.r01.ru |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.r01.ru, ns1.r01.ru)
Analysis
IP Addresses
ah33.ru points to a single IP number: 195.24.68.11.
Other host names, for instance ekra-adr.ru, medagent.su, peterkolchin.ru, kavayno.ru and ysd.ru share IP numbers with ah33.ru.
Name Servers
Delegation for ah33.ru rests with two name servers, ns1.r01.ru and ns2.r01.ru.
ah33.ru shares the same name server setup as other domains, including xn----9sbelq0cebed3j.xn--p1ai, rifor12.ru, nolaw.ru, jprom.ru and chinaport.ru.
Host names with one IP number: ns1.r01.ru points to 31.177.80.41; ns2.r01.ru points to 31.177.76.41.
Mail Servers
ah33.ru is handled by a single mail server, mx.yandex.net.
ah33.ru uses the same mail server configuration as other domains, such as tech-ud72.ru, ankaraicmimarlik.com.tr, hamravesh.ir, mbmd.ru and arkabahce.com.tr.
ah33.ru shares some mail servers with other domains at least partially, for example isafeco.net.
mx.yandex.net resolves to two IP numbers: 2a02:6b8::311 and 77.88.21.249.