adminify.su - dns.ninja
adminify.su
su
| 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=650210791 | ||||||
Same first word
Similar names
Previous names
adj.su |
adjika.su |
adk.su |
adktrans.su |
adl.su |
adler.su |
adline.su |
adm-tayga.su |
adm.su |
admag.su |
adme.su |
admedicine.su |
admi.su |
admin-domen.su |
admin.su |
admin1c.su |
admin24.su |
adminbot.su |
Next names
DNS History
9 records (9 active, 0 former)
●MXmx1.beget.com2026-09-25 → 2026-10-01 · 4 obs
○ 2026-09-29 15:13:36
● 2026-09-29 20:45:10
● 2026-10-01 19:31:16
●MXmx2.beget.com2026-09-25 → 2026-10-01 · 4 obs
○ 2026-09-29 15:13:36
● 2026-09-29 20:45:10
● 2026-10-01 19:31:16
●A94.183.236.1602026-09-25 → 2026-10-01 · 4 obs
○ 2026-09-29 15:13:36
● 2026-09-29 20:45:10
● 2026-10-01 19:31:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| su | a.dns.ripn.net, c.tld-servers.ru, b.dns.ripn.net, d.dns.ripn.net... | 12 records |
| adminify.su | ns2.beget.ru, ns1.beget.com, ns1.beget.ru, ns1.beget.pro... | - |
✅ Authoritative Response
Server:93.92.81.0
NS records: ns2.beget.ru, ns1.beget.com, ns1.beget.ru, ns1.beget.pro, ns2.beget.pro, ns2.beget.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for adminify.su (unsigned zone)
⏱️ Timing
Total: 1854ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 94.183.236.160 |
| 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 |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (f.dns.ripn.net, e.dns.ripn.net, d.dns.ripn.net...)
Analysis
IP Addresses
adminify.su resolves to just one IP address, 94.183.236.160.
Name Servers
The DNS delegation for adminify.su covers 6 name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro and 3 more.
adminify.su has at least partial name server overlap with other domains, such as proschai-shkola.ru, dstrc.su, dar-vetclinic.ru and two others.
These name servers tend to appear together with the name servers ns2.beget.pro, ns1.beget.ru and ns2.beget.ru.
Host names that point to 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.
Each of ns2.beget.com, ns2.beget.pro and ns2.beget.ru resolves to 185.50.27.12.
Mail Servers
adminify.su is served by two mail servers, mx1.beget.com and mx2.beget.com.
Among the domains sharing a mail server setup with adminify.su are quixarplendio.store, xn--78-mlc1ajfhs2a.xn--p1ai, lentopilnyi-stanok.ru and two others.
Hosts mx1.beget.com and mx2.beget.com resolve to four IP addresses each: mx1.beget.com points to 5.101.158.67, 5.101.158.68, 185.78.30.95 and 185.78.30.126, whereas mx2.beget.com points to 185.78.30.48, 185.78.30.71, 185.78.30.95 and 185.78.30.126.
These two host names — mx1.beget.com and mx2.beget.com — each point to 185.78.30.95 IP addresses.
These two host names — mx1.beget.com and mx2.beget.com — each point to 185.78.30.126 IP addresses.