fighter.ru - dns.ninja
fighter.ru
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns.omsk.ru ⚠️ Not in zone NS records | ||||||
| A | 85.28.0.130🇷🇺 GES-AS85.28.0.0/21 IMASTER Network | ||||||
| PTR | ltusm2.omsk.ru | ||||||
| PTR | ns.omsk.ru | ||||||
| A | 217.151.16.130🇷🇺 GES-AS217.151.16.0/21 IMASTER Network | ||||||
| PTR | ns.imaster.ru | ||||||
| NS | ns1.omsk.ru ⚠️ Not in zone NS records | ||||||
| A | 85.28.1.130🇷🇺 GES-AS85.28.0.0/21 IMASTER Network | ||||||
| PTR | ns1.omsk.ru | ||||||
| A | 217.151.17.130🇷🇺 GES-AS217.151.16.0/21 IMASTER Network | ||||||
| PTR | ns1.omsk.ru | ||||||
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=4069777 | ||||||
Same first word
Similar names
DNS History
10 records (2 active, 8 former)
○NSdnsproxy1.fm.nic.ru2026-06-15 → 2026-06-15 · 4 obs
● 2026-06-15 13:12:28
○ 2026-07-14 02:07:06
○ 2026-07-28 09:43:08
○NSdnsproxy2.fm.nic.ru2026-06-15 → 2026-06-15 · 4 obs
● 2026-06-15 13:12:28
○ 2026-07-14 02:07:06
○ 2026-07-28 09:43:08
○NSgameshop.ru2015-07-06 → 2017-01-25 · 4 obs
● 2017-01-25 07:53:08
○ 2026-06-15 13:12:28
○ 2026-07-28 09:43:08
●NSns.omsk.ru2015-07-06 → 2026-07-28 · 5 obs
● 2017-01-25 07:53:08
○ 2026-06-15 13:12:28
● 2026-07-14 02:07:06
● 2026-07-28 09:43:08
●NSns1.omsk.ru2015-07-06 → 2026-07-28 · 5 obs
● 2017-01-25 07:53:08
○ 2026-06-15 13:12:28
● 2026-07-14 02:07:06
● 2026-07-28 09:43:08
○MXgameshop.ru2015-07-06 → 2017-01-25 · 4 obs
● 2017-01-25 07:53:08
○ 2026-06-15 13:12:28
○ 2026-07-28 09:43:08
○MXnomail.nic.ru2026-06-15 → 2026-06-15 · 4 obs
● 2026-06-15 13:12:28
○ 2026-07-14 02:07:06
○ 2026-07-28 09:43:08
○A31.177.76.322026-06-15 → 2026-06-15 · 4 obs
● 2026-06-15 13:12:28
○ 2026-07-14 02:07:06
○ 2026-07-28 09:43:08
○A31.177.80.322026-06-15 → 2026-06-15 · 4 obs
● 2026-06-15 13:12:28
○ 2026-07-14 02:07:06
○ 2026-07-28 09:43:08
○A89.108.110.1672015-07-06 → 2017-01-25 · 4 obs
● 2017-01-25 07:53:08
○ 2026-06-15 13:12:28
○ 2026-07-28 09:43:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | d.dns.ripn.net, f.dns.ripn.net, b.dns.ripn.net, a.dns.ripn.net... | - |
| fighter.ru | ns1.omsk.ru, ns.omsk.ru | 2 records |
✅ Authoritative Response
Server:217.151.17.130
NS records: ns1.omsk.ru, ns.omsk.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fighter.ru (unsigned zone)
⏱️ Timing
Total: 1462ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.omsk.ru, ns.omsk.ru)
Analysis
Name Servers
The NS records for fighter.ru delegate to ns1.omsk.ru and ns.omsk.ru.
fighter.ru shares its name server setup with other domains, including 11.28.85.in-addr.arpa, 0.28.85.in-addr.arpa, 1.28.85.in-addr.arpa and two others.
fighter.ru partially shares its NS delegation with several other domains, including whyberg.ru, sib-ix.ru, ukstargorod.ru and two others.
In DNS configurations, these name servers often share authority with ns1.imaster.ru, ns.imaster.ru, ns3.cocos.ru and 4 other name servers.
ns1.omsk.ru resolves to 85.28.1.130 and 217.151.17.130. Likewise, ns.omsk.ru resolves to 85.28.0.130 and 217.151.16.130 — two IP addresses apiece.