fm373.net - robtex.com
fm373.net
net
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774668057 | ||||||
Same first word
fm373.net |
DNS History
16 records (4 active, 12 former)
○NSns1.agava.net.ru2015-06-27 → 2016-11-26 · 4 obs
● 2016-11-26 10:23:48
○ 2017-06-24 08:21:18
○ 2026-03-28 03:50:50
●NSns1.reg.ru2017-06-24 → 2026-03-28 · 3 obs
● 2017-06-24 08:21:18
● 2026-03-28 03:50:50
○NSns2.agava.net.ru2015-06-27 → 2016-11-26 · 4 obs
● 2016-11-26 10:23:48
○ 2017-06-24 08:21:18
○ 2026-03-28 03:50:50
●NSns2.reg.ru2017-06-24 → 2026-03-28 · 3 obs
● 2017-06-24 08:21:18
● 2026-03-28 03:50:50
○MXalt1.aspmx.l.google.com2015-06-27 → 2015-06-27 · 3 obs
○ 2015-11-09 13:28:34
○ 2026-03-28 03:50:50
○MXalt2.aspmx.l.google.com2015-06-27 → 2015-06-27 · 3 obs
○ 2015-11-09 13:28:34
○ 2026-03-28 03:50:50
○MXaspmx.l.google.com2015-06-27 → 2015-06-27 · 3 obs
○ 2015-11-09 13:28:34
○ 2026-03-28 03:50:50
○MXaspmx2.googlemail.com2015-06-27 → 2015-06-27 · 3 obs
○ 2015-11-09 13:28:34
○ 2026-03-28 03:50:50
○MXaspmx3.googlemail.com2015-06-27 → 2015-06-27 · 3 obs
○ 2015-11-09 13:28:34
○ 2026-03-28 03:50:50
○MXcluster.relay.agava.net2015-06-27 → 2015-06-27 · 3 obs
○ 2015-11-09 13:28:34
○ 2026-03-28 03:50:50
●MXmx.yandex.ru2015-11-09 → 2026-03-28 · 3 obs
● 2015-11-09 13:28:34
● 2026-03-28 03:50:50
○A2a03:4900:0:6037:80:78:250:172015-06-27 → 2015-06-27 · 3 obs
○ 2015-11-09 13:28:34
○ 2026-03-28 03:50:50
●A46.39.241.1162018-07-10 → 2026-03-28 · 3 obs
● 2018-07-10 14:09:38
● 2026-03-28 03:50:50
○A54.183.231.1162015-11-09 → 2015-11-09 · 4 obs
● 2015-11-09 13:28:34
○ 2016-02-03 05:59:56
○ 2026-03-28 03:50:50
○A80.243.12.1262016-02-03 → 2017-06-24 · 5 obs
● 2016-02-03 05:59:56
● 2017-06-24 08:21:18
○ 2018-07-10 14:09:38
○ 2026-03-28 03:50:50
○A89.108.67.652015-06-27 → 2015-06-27 · 3 obs
○ 2015-11-09 13:28:34
○ 2026-03-28 03:50:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | d.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, l.gtld-servers.net... | - |
| fm373.net | ns1.reg.ru, ns2.reg.ru | - |
✅ Authoritative Response
Server:176.99.13.11
NS records: ns1.reg.ru, ns2.reg.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fm373.net (unsigned zone)
⏱️ Timing
Total: 2344ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 46.39.241.116 |
| NS | 2 | ns1.reg.ru, ns2.reg.ru |
| MX | 1 | mx.yandex.ru (pri: 10) |
| SOA | 1 | ns1.reg.ru hostmaster.ns1.reg.ru |
Analysis
IP Addresses
fm373.net points to a single IP: 46.39.241.116.
Name Servers
Two name servers ns1.reg.ru and ns2.reg.ru handle delegation for fm373.net.
fm373.net uses the same name server setup as other domains, for example krasnayapolyana.game, tvoybanket.ru, pp-design.ru, meredov.ru and epicweb.ru.
Host names with ten IP numbers:
ns1.reg.ru points to 2a00:f940:9::1:1, 2a00:f940:9::2:1, 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15 and 194.58.117.17.
ns2.reg.ru points to 2a00:f940:9::1:2, 2a00:f940:9::2:2, 176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16 and 194.58.117.18.
Mail Servers
fm373.net is handled by a single mail server, mx.yandex.ru.
fm373.net has the same mail server setup as other domains, including backups.cd, na93.ru, rst-team.ru, rsn.krasnodar.ru and sdenisov.ru.
fm373.net shares at least partially some mail servers with other domains, for instance virty.io and bormaster.ru.
Host mx.yandex.ru resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.