avenbot.ru - dns.ninja
avenbot.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 135.106.146.94🇺🇸 ENETWORKS128.0.0.0/2 | ||||||
| NS | ns1.beget.com ⭐ | ||||||
| A | 93.92.81.0 | ||||||
| NS | ns1.beget.pro | ||||||
| A | 93.92.81.0 | ||||||
| NS | ns1.beget.ru | ||||||
| A | 5.101.159.11🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU | ||||||
| PTR | ns1.beget.com | ||||||
| NS | ns2.beget.com | ||||||
| A | 185.50.27.12🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU | ||||||
| PTR | ns2.beget.com | ||||||
| NS | ns2.beget.pro | ||||||
| A | 185.50.27.12🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU | ||||||
| PTR | ns2.beget.com | ||||||
| NS | ns2.beget.ru | ||||||
| A | 185.50.27.12🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU | ||||||
| PTR | ns2.beget.com | ||||||
| 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 | v=spf1 ip4:45.134.14.20 include:_spf.yandex.net ~all | ||||||
| SOA | ns1.beget.comhostmaster@beget.com serial=1780934072 | ||||||
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | c.tld-servers.ru | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4069972 | ||||||
Same first word
Similar names
DNS History
9 records (8 active, 1 former)
●MXmx.yandex.net2026-05-10 → 2026-08-13 · 2 obs
● 2026-08-13 13:03:40
●A135.106.146.942026-07-01 → 2026-08-13 · 3 obs
● 2026-07-01 16:11:38
● 2026-08-13 13:03:40
○A185.248.102.1302026-05-10 → 2026-06-05 · 4 obs
● 2026-06-05 14:08:18
○ 2026-07-01 16:11:38
○ 2026-08-13 13:03:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | d.dns.ripn.net, a.dns.ripn.net, b.dns.ripn.net, c.tld-servers.ru... | - |
| avenbot.ru | ns1.beget.ru, ns1.beget.com, ns1.beget.pro, ns2.beget.ru... | 3 records |
✅ Authoritative Response
Server:185.50.27.12
NS records: ns1.beget.ru, ns1.beget.com, ns1.beget.pro, ns2.beget.ru, ns2.beget.com, ns2.beget.pro
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for avenbot.ru (unsigned zone)
⏱️ Timing
Total: 1497ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 135.106.146.94 |
| NS | 6 | ns2.beget.ru, ns1.beget.ru... |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | v=spf1 ip4:45.134.14.20 include:_spf.yan |
| SOA | 1 | ns1.beget.com hostmaster.beget.com |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.beget.ru, ns1.beget.ru, ns2.beget.ru)
Analysis
IP Addresses
avenbot.ru resolves to one IP address: 135.106.146.94.
Name Servers
The DNS delegation for avenbot.ru covers 6 name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro and 3 more.
The name servers of avenbot.ru overlap at least partially with those of other domains — among them logiq.ru, semeyka-croods-lordfilms.ru, s12v.ru and two more.
The name servers ns2.beget.pro, ns1.beget.ru and ns2.beget.ru are commonly seen alongside these name servers.
Hosts with just one IP address:
ns1.beget.com points to the IP address 93.92.81.0.
ns2.beget.com points to the IP address 185.50.27.12.
ns1.beget.pro points to the IP address 93.92.81.0.
ns2.beget.pro points to the IP address 185.50.27.12.
ns1.beget.ru points to the IP address 5.101.159.11.
ns2.beget.ru points to the IP address 185.50.27.12.
These two host names — ns1.beget.com and ns1.beget.pro — each point to 93.92.81.0 IP addresses.
The host names ns2.beget.com, ns2.beget.pro and ns2.beget.ru each resolve to 185.50.27.12.
Mail Servers
Mail for avenbot.ru is handled by a single mail server, mx.yandex.net.
avenbot.ru uses an identical mail server configuration to several other domains — among them goldbustravel.com, nguoikimboi.com, eksenmakina.net and two more.
avenbot.ru partially shares its mail servers with other domains — including cupe.spb.ru, city-print.com.ua, truboprovod.by and b14esh.com.
mx.yandex.net resolves to two IP numbers — 77.88.21.249 and 2a02:6b8::311.