monitoring33.ru - robtex.com
monitoring33.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 45.130.41.13🇷🇺 BEGET-AS45.130.41.0/24 BEGET.RU | ||||||
| NS | ns1.beget.com ⭐ | ||||||
| A | 5.101.159.11🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU | ||||||
| PTR | ns1.beget.com | ||||||
| NS | ns1.beget.pro | ||||||
| A | 5.101.159.11🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU | ||||||
| PTR | ns1.beget.com | ||||||
| A | 93.92.81.0 | ||||||
| NS | ns1.beget.ru ⚠️ Not in parent delegation | ||||||
| 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 ⚠️ Not in parent delegation | ||||||
| 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 redirect=_spf.yandex.net | ||||||
| SOA | ns1.beget.comhostmaster@beget.com serial=1660842335 | ||||||
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=4068815 | ||||||
Same first word
monitoring33.ru |
DNS History
15 records (8 active, 7 former)
○NSdns1.yandex.net2015-07-01 → 2017-06-26 · 6 obs
● 2016-04-26 02:46:32
○ 2016-12-05 18:39:48
● 2017-06-26 16:51:38
○ 2026-02-18 16:30:50
○ 2026-05-09 20:41:50
○NSdns2.yandex.net2016-04-26 → 2017-06-26 · 6 obs
● 2016-04-26 02:46:32
○ 2016-12-05 18:39:48
● 2017-06-26 16:51:38
○ 2026-02-18 16:30:50
○ 2026-05-09 20:41:50
●NSns1.beget.com2026-02-18 → 2026-05-09 · 3 obs
● 2026-02-18 16:30:50
● 2026-05-09 20:41:50
●NSns1.beget.pro2026-02-18 → 2026-05-09 · 3 obs
● 2026-02-18 16:30:50
● 2026-05-09 20:41:50
●NSns1.beget.ru2026-02-18 → 2026-05-09 · 3 obs
● 2026-02-18 16:30:50
● 2026-05-09 20:41:50
○NSns1.itnet33.ru2015-07-01 → 2016-12-05 · 7 obs
○ 2015-11-09 06:35:34
● 2016-02-01 00:46:40
○ 2016-04-26 02:46:32
● 2016-12-05 18:39:48
○ 2017-06-26 16:51:38
○ 2026-05-09 20:41:50
●NSns2.beget.com2026-02-18 → 2026-05-09 · 3 obs
● 2026-02-18 16:30:50
● 2026-05-09 20:41:50
●NSns2.beget.pro2026-02-18 → 2026-05-09 · 3 obs
● 2026-02-18 16:30:50
● 2026-05-09 20:41:50
●NSns2.beget.ru2026-02-18 → 2026-05-09 · 3 obs
● 2026-02-18 16:30:50
● 2026-05-09 20:41:50
○NSns2.itnet33.ru2015-07-01 → 2016-12-05 · 6 obs
● 2016-02-01 00:46:40
○ 2016-04-26 02:46:32
● 2016-12-05 18:39:48
○ 2017-06-26 16:51:38
○ 2026-05-09 20:41:50
●MXmx.yandex.net2015-07-01 → 2026-05-09 · 4 obs
○ 2015-11-09 06:35:34
● 2016-02-01 00:46:40
● 2026-05-09 20:41:50
○MXmx.yandex.ru2015-11-09 → 2015-11-09 · 4 obs
● 2015-11-09 06:35:34
○ 2016-02-01 00:46:40
○ 2026-05-09 20:41:50
○A109.201.97.242015-11-09 → 2017-06-26 · 7 obs
● 2015-11-09 06:35:34
○ 2016-02-01 00:46:40
● 2016-04-26 02:46:32
● 2017-06-26 16:51:38
○ 2026-02-18 16:30:50
○ 2026-05-09 20:41:50
○A109.201.98.1162015-07-01 → 2015-07-01 · 3 obs
○ 2017-06-26 16:51:38
○ 2026-05-09 20:41:50
●A45.130.41.132026-02-18 → 2026-05-09 · 3 obs
● 2026-02-18 16:30:50
● 2026-05-09 20:41: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... | - |
| monitoring33.ru | ns1.beget.pro, ns1.beget.com, ns2.beget.pro, ns2.beget.com | - |
✅ Authoritative Response
Server:5.101.159.11
NS records: ns1.beget.pro, ns1.beget.com, ns2.beget.pro, ns2.beget.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for monitoring33.ru (unsigned zone)
⏱️ Timing
Total: 1216ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.130.41.13 |
| NS | 6 | ns1.beget.com, ns2.beget.com... |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | v=spf1 redirect=_spf.yandex.net |
| SOA | 1 | ns1.beget.com hostmaster.beget.com |
Analysis
IP Addresses
monitoring33.ru points to a single IP: 45.130.41.13.
Other host names, for instance schoolpsy.ru, xavia.ru, botano.ru, grodno.potolki-perimetr.by and www.evle.ru share IP numbers with monitoring33.ru.
Name Servers
monitoring33.ru is delegated to six name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro, ns2.beget.pro, ns1.beget.ru and ns2.beget.ru.
monitoring33.ru at least partially shares its name servers with other domains, for instance lechenie-narkomanii-ekaterinburg0.ru, hiddenmindpower.com, beneffis.ru, ko-st.ru and naturelika.com.
Host names with two IP numbers: ns1.beget.pro points to 5.101.159.11 and 93.92.81.0.
Host names with one IP number: ns1.beget.com points to 5.101.159.11; ns2.beget.com points to 185.50.27.12; ns2.beget.pro points to 185.50.27.12; ns1.beget.ru points to 5.101.159.11; ns2.beget.ru points to 185.50.27.12.
Host names pointing to 5.101.159.11: ns1.beget.pro, ns1.beget.com and ns1.beget.ru.
Host names pointing to 185.50.27.12: ns2.beget.com, ns2.beget.pro and ns2.beget.ru.
Mail Servers
monitoring33.ru is served by a single mail server, mx.yandex.net.
monitoring33.ru uses the same mail server setup as other domains such as domamir.by, hotelbravis.ru, apoly.ru, yakgaz.com and konditer-priroda.ru.
monitoring33.ru shares some mail servers with other domains, including rakiosk.ru, fylgja.ru, to-text.ru, webursitet.ru and cprprint.ru.
Hostname mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.