adminwp.ru - dns.ninja
adminwp.ru
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=4069247 | ||||||
Same first word
Similar names
DNS History
12 records (9 active, 3 former)
●NSns1.beget.com2026-04-18 → 2026-06-14 · 3 obs
● 2026-04-18 12:57:06
● 2026-06-14 04:52:52
●NSns1.beget.pro2026-04-18 → 2026-06-14 · 3 obs
● 2026-04-18 12:57:06
● 2026-06-14 04:52:52
●NSns1.beget.ru2026-04-18 → 2026-06-14 · 3 obs
● 2026-04-18 12:57:06
● 2026-06-14 04:52:52
○NSns1.reg.ru2015-07-24 → 2015-11-30 · 4 obs
● 2015-11-30 02:29:02
○ 2016-06-30 09:20:28
○ 2026-06-14 04:52:52
●NSns2.beget.com2026-04-18 → 2026-06-14 · 3 obs
● 2026-04-18 12:57:06
● 2026-06-14 04:52:52
●NSns2.beget.pro2026-04-18 → 2026-06-14 · 3 obs
● 2026-04-18 12:57:06
● 2026-06-14 04:52:52
●NSns2.beget.ru2026-04-18 → 2026-06-14 · 3 obs
● 2026-04-18 12:57:06
● 2026-06-14 04:52:52
○NSns2.reg.ru2015-07-24 → 2015-11-30 · 4 obs
● 2015-11-30 02:29:02
○ 2016-06-30 09:20:28
○ 2026-06-14 04:52:52
○A31.31.204.592015-07-24 → 2015-11-30 · 4 obs
● 2015-11-30 02:29:02
○ 2016-06-30 09:20:28
○ 2026-06-14 04:52:52
●A45.130.41.72026-04-18 → 2026-06-14 · 3 obs
● 2026-04-18 12:57:06
● 2026-06-14 04:52:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | d.dns.ripn.net, b.dns.ripn.net, f.dns.ripn.net, e.dns.ripn.net... | - |
| adminwp.ru | ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro | - |
✅ Authoritative Response
Server:185.50.27.12
NS records: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for adminwp.ru (unsigned zone)
⏱️ Timing
Total: 1876ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.130.41.7 |
| NS | 6 | ns2.beget.ru, ns1.beget.ru... |
| MX | 2 | mx1.beget.com (pri: 10), mx2.beget.com (pri: 20) |
| TXT | 1 | v=spf1 redirect=beget.com |
| SOA | 1 | ns1.beget.com hostmaster.beget.com |
Analysis
IP Addresses
adminwp.ru has exactly one IP address — 45.130.41.7.
hats-service.ru, xn--80ag1a2a.xn--p1ai, xn--c1aafnnrb2l.xn--p1ai plus two other host names have IP numbers in common with adminwp.ru.
Name Servers
DNS for adminwp.ru is handled by 6 name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro and 3 others.
At least some of adminwp.ru's name servers are shared with other domains, for example xn--80ae0baobd.xn--p1ai, labubi.ru, ek-m.ru and two more.
It is common for these name servers to be used in conjunction with the name servers ns2.beget.pro, ns1.beget.ru and ns2.beget.ru.
Host names with one IP number:
ns1.beget.com directs to 93.92.81.0.
ns2.beget.com directs to 185.50.27.12.
ns1.beget.pro directs to 93.92.81.0.
ns2.beget.pro directs to 185.50.27.12.
ns1.beget.ru directs to 5.101.159.11.
ns2.beget.ru directs to 185.50.27.12.
Host names pointing to 93.92.81.0 IP addresses: ns1.beget.com and ns1.beget.pro.
Three host names point to 185.50.27.12: ns2.beget.com, ns2.beget.pro and ns2.beget.ru.
Mail Servers
adminwp.ru uses two mail servers, mx1.beget.com and mx2.beget.com.
The mail server setup of adminwp.ru matches that of other domains such as salonspektr.ru, med-like.ru, xn--80aax7ahr.xn--p1ai and two others.
At least a portion of adminwp.ru's mail servers are shared with other domains, among them herhis.ru and fishout.ru.
The hosts mx1.beget.com and mx2.beget.com each resolve to four IP addresses: mx1.beget.com points to 5.101.158.67, 5.101.158.68, 185.78.30.95 and 185.78.30.126 while mx2.beget.com points to 185.78.30.48, 185.78.30.71, 185.78.30.95 and 185.78.30.126.
Host names pointing to 185.78.30.95 IP addresses: mx1.beget.com and mx2.beget.com.
Host names pointing to 185.78.30.126 IP addresses: mx1.beget.com and mx2.beget.com.