ferrocom.org - dns.ninja
ferrocom.org
org
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a2.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | b0.org.afilias-nst.org | ||||||
| NS | b2.org.afilias-nst.org | ||||||
| NS | c0.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | d0.org.afilias-nst.org | ||||||
| SOA | a0.org.afilias-nst.infohostmaster@donuts.email serial=1781869530 | ||||||
Same first word
Similar names
DNS History
9 records (7 active, 2 former)
●NSns1.hosting.reg.ru2020-02-05 → 2026-06-19 · 2 obs
● 2026-06-19 11:55:00
●NSns2.hosting.reg.ru2020-02-05 → 2026-06-19 · 2 obs
● 2026-06-19 11:55:00
●NSvip224.hosting.reg.ru2026-02-14 → 2026-06-19 · 3 obs
● 2026-02-14 18:05:46
● 2026-06-19 11:55:00
○MXmx.yandex.net2020-02-05 → 2020-02-05 · 3 obs
○ 2026-02-14 18:05:46
○ 2026-06-19 11:55:00
●MXmx1.hosting.reg.ru2026-02-14 → 2026-06-19 · 3 obs
● 2026-02-14 18:05:46
● 2026-06-19 11:55:00
●MXmx2.hosting.reg.ru2026-02-14 → 2026-06-19 · 3 obs
● 2026-02-14 18:05:46
● 2026-06-19 11:55:00
●A2a00:f940:2:2:1:3:0:2242026-02-14 → 2026-06-19 · 3 obs
● 2026-02-14 18:05:46
● 2026-06-19 11:55:00
○A37.140.192.1232020-02-05 → 2020-02-05 · 3 obs
○ 2026-02-14 18:05:46
○ 2026-06-19 11:55:00
●A37.140.192.2162026-02-14 → 2026-06-19 · 3 obs
● 2026-02-14 18:05:46
● 2026-06-19 11:55:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| org | b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org | - |
| ferrocom.org | ns1.hosting.reg.ru, ns2.hosting.reg.ru | - |
✅ Authoritative Response
Server:31.31.194.244
NS records: ns1.hosting.reg.ru, ns2.hosting.reg.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ferrocom.org (unsigned zone)
⏱️ Timing
Total: 1549ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 37.140.192.216 |
| AAAA | 1 | 2a00:f940:2:2:1:3:0:224 |
| NS | 2 | ns1.hosting.reg.ru, ns2.hosting.reg.ru |
| MX | 2 | mx1.hosting.reg.ru (pri: 10), mx2.hosting.reg.ru (pri: 15) |
| TXT | 1 | v=spf1 ip4:37.140.192.216 ip4:62.182.158 |
| SOA | 1 | vip224.hosting.reg.ru support.reg.ru |
Analysis
IP Addresses
ferrocom.org points to the IP addresses 37.140.192.216 and 2a00:f940:2:2:1:3:0:224
raskrutivideo.ru, mail.primelr.ru, vasilinabaranova.ru and two other host names share IP numbers with ferrocom.org.
Name Servers
ferrocom.org is delegated to three name servers: ns1.hosting.reg.ru, ns2.hosting.reg.ru and vip224.hosting.reg.ru.
At least some of ferrocom.org's name servers are shared with other domains, for example transoft.ru, partnerschool.ru, vikastyle.ru and two more.
These name servers tend to co-occur with server256.hosting.reg.ru, server152.hosting.reg.ru, vip233.hosting.reg.ru and 6 other name servers in the same DNS delegations.
Hostnames that resolve to 14 IP addresses:
ns1.hosting.reg.ru resolves to 31.31.194.245, 31.31.194.251, 31.31.196.37 and 11 other IP addresses.
ns2.hosting.reg.ru resolves to 31.31.194.244, 31.31.196.34, 31.31.196.53 and 11 other IP addresses.
Hosts with just one IP address:
vip224.hosting.reg.ru points to 37.140.192.216.
Mail Servers
Mail for ferrocom.org is handled by two mail servers — mx1.hosting.reg.ru and mx2.hosting.reg.ru.
ferrocom.org uses an identical mail server configuration to several other domains — among them ct-service.ru, np-moash.ru, testlime.ru and two more.
ferrocom.org has at least partial mail server overlap with other domains such as u4eba.net, apibol.ru, simonov.org and two more.
mx1.hosting.reg.ru and mx2.hosting.reg.ru each resolve to two IP addresses: 31.31.194.240 and 31.31.194.241.
mx1.hosting.reg.ru and mx2.hosting.reg.ru are host names that each point to 31.31.194.240 IP addresses.
mx1.hosting.reg.ru and mx2.hosting.reg.ru are host names that each point to 31.31.194.241 IP addresses.