status37.com - robtex.com
status37.com
com
| 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=1776214977 | ||||||
Same first word
status37.com |
Similar names
DNS History
14 records (4 active, 10 former)
○NSns1.beget.com2017-03-30 → 2017-03-30 · 4 obs
● 2017-03-30 10:57:54
○ 2026-02-24 09:15:34
○ 2026-04-15 01:32:24
○NSns1.beget.pro2015-07-13 → 2017-03-30 · 4 obs
● 2017-03-30 10:57:54
○ 2026-02-24 09:15:34
○ 2026-04-15 01:32:24
○NSns1.beget.ru2015-07-13 → 2016-07-03 · 4 obs
● 2016-07-03 11:48:46
○ 2017-03-30 10:57:54
○ 2026-04-15 01:32:24
●NSns1.reg.ru2026-02-24 → 2026-04-15 · 3 obs
● 2026-02-24 09:15:34
● 2026-04-15 01:32:24
○NSns2.beget.com2017-03-30 → 2017-03-30 · 4 obs
● 2017-03-30 10:57:54
○ 2026-02-24 09:15:34
○ 2026-04-15 01:32:24
○NSns2.beget.pro2015-07-13 → 2017-03-30 · 4 obs
● 2017-03-30 10:57:54
○ 2026-02-24 09:15:34
○ 2026-04-15 01:32:24
○NSns2.beget.ru2015-07-13 → 2016-07-03 · 4 obs
● 2016-07-03 11:48:46
○ 2017-03-30 10:57:54
○ 2026-04-15 01:32:24
●NSns2.reg.ru2026-02-24 → 2026-04-15 · 3 obs
● 2026-02-24 09:15:34
● 2026-04-15 01:32:24
●MXmx.yandex.net2026-02-24 → 2026-04-15 · 3 obs
● 2026-02-24 09:15:34
● 2026-04-15 01:32:24
○MXmx1.beget.ru2015-07-13 → 2017-03-30 · 4 obs
● 2017-03-30 10:57:54
○ 2026-02-24 09:15:34
○ 2026-04-15 01:32:24
○MXmx2.beget.ru2015-07-13 → 2017-03-30 · 4 obs
● 2017-03-30 10:57:54
○ 2026-02-24 09:15:34
○ 2026-04-15 01:32:24
●A185.215.4.142026-02-24 → 2026-04-15 · 3 obs
● 2026-02-24 09:15:34
● 2026-04-15 01:32:24
○A5.101.152.532015-07-13 → 2016-07-03 · 4 obs
● 2016-07-03 11:48:46
○ 2017-03-30 10:57:54
○ 2026-04-15 01:32:24
○A5.101.152.832017-03-30 → 2017-03-30 · 4 obs
● 2017-03-30 10:57:54
○ 2026-02-24 09:15:34
○ 2026-04-15 01:32:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| status37.com | 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 status37.com (unsigned zone)
⏱️ Timing
Total: 753ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.215.4.14 |
| NS | 2 | ns1.reg.ru, ns2.reg.ru |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 2 | v=spf1 redirect=_spf.yandex.net, yandex-verification: e0f5af943719fa97 |
| SOA | 1 | ns1.reg.ru hostmaster.ns1.reg.ru |
Analysis
IP Addresses
status37.com resolves to a single IP: 185.215.4.14.
Other host names, for instance oooiks.ru, mediaks.ru, www.gardinia.su, www.ldiss.rsl.ru and premiera.club share IP numbers with status37.com.
Name Servers
status37.com has two name servers: ns1.reg.ru and ns2.reg.ru.
status37.com shares the same name server setup as other domains, for example levitsky.ru, kamagra.ru, dmffx.com, krivoy-rog-news.ru and organicfarm.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
status37.com is handled by a single mail server, mx.yandex.net.
status37.com shares the mail server setup with other domains, for example vtigroup.ru, simdimuzik.com, motorhaus.ru, suelektro.ru and rolety.by.
status37.com shares mail servers with other domains at least partially, for example redpoints.ru, profatom.ru, bakirovo.com and garrend.com.
mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.