servermonitoring.me - dns.ninja
servermonitoring.me
| DNSSEC | ⚠️ Not signed | ||||||
| A | 51.158.210.108🇫🇷 AS1287651.158.128.0/17 SCALEWAY Amsterdam, Netherlands | ||||||
| PTR | 108-210-158-51.instances.scw.cloud | ||||||
| NS | jake.datasec.sh ⭐ | ||||||
| A | 51.158.190.33🇫🇷 AS1287651.158.128.0/17 SCALEWAY Amsterdam, Netherlands | ||||||
| PTR | 33-190-158-51.instances.scw.cloud | ||||||
| NS | kate.datasec.sh | ||||||
| A | 51.15.100.248🇫🇷 AS1287651.15.0.0/17 SCALEWAY Amsterdam, Netherlands | ||||||
| PTR | 248-100-15-51.instances.scw.cloud | ||||||
| SOA | jake.datasec.shdns@datasec.sh 2025-03-06 #19 | ||||||
me
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.nic.me ⭐ | ||||||
| NS | a2.nic.me | ||||||
| NS | b0.nic.me | ||||||
| NS | b2.nic.me | ||||||
| NS | c0.nic.me | ||||||
| SOA | a0.nic.mehostmaster@donuts.email serial=1786243116 | ||||||
Same first word
servermonitoring.at |
servermonitoring.me |
servermonitoring.in |
servermonitoring.io |
servermonitoring.ir |
servermonitoring.com |
servermonitoring.co.uk |
Similar names
DNS History
25 records (3 active, 22 former)
○NSdana.ns.cloudflare.com2021-09-09 → 2021-09-09 · 4 obs
● 2021-09-09 21:25:58
○ 2026-02-26 19:21:48
○ 2026-08-09 02:51:00
●NSjake.datasec.sh2026-02-26 → 2026-08-09 · 3 obs
● 2026-02-26 19:21:48
● 2026-08-09 02:51:00
●NSkate.datasec.sh2026-02-26 → 2026-08-09 · 3 obs
● 2026-02-26 19:21:48
● 2026-08-09 02:51:00
○NSns1.tulipsdns.com2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSns2.tulipsdns.com2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSns3.tulipsdns.com2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSns4.tulipsdns.com2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSns5.tulipsdns.com2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSns6.tulipsdns.com2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSns7.tulipsdns.com2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSpns1.cloudns.net2015-07-09 → 2015-12-11 · 4 obs
● 2015-12-11 13:59:28
○ 2016-03-28 01:05:42
○ 2026-08-09 02:51:00
○NSpns10.cloudns.net2016-03-28 → 2016-06-16 · 5 obs
● 2016-03-28 01:05:42
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSpns4.cloudns.net2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSpns8.cloudns.net2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○NSpns9.cloudns.net2015-07-09 → 2015-12-11 · 4 obs
● 2015-12-11 13:59:28
○ 2016-03-28 01:05:42
○ 2026-08-09 02:51:00
○NStom.ns.cloudflare.com2021-09-09 → 2021-09-09 · 4 obs
● 2021-09-09 21:25:58
○ 2026-02-26 19:21:48
○ 2026-08-09 02:51:00
○MXbrescia.fez.bz2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○MXmail.servermonitoring.me2015-07-09 → 2016-06-16 · 4 obs
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○A104.21.51.562021-09-09 → 2021-09-09 · 4 obs
● 2021-09-09 21:25:58
○ 2026-02-26 19:21:48
○ 2026-08-09 02:51:00
○A172.67.221.1682021-09-09 → 2021-09-09 · 4 obs
● 2021-09-09 21:25:58
○ 2026-02-26 19:21:48
○ 2026-08-09 02:51:00
○A212.83.174.2272015-09-27 → 2016-06-16 · 5 obs
● 2015-09-27 23:03:20
● 2016-06-16 05:55:46
○ 2021-09-09 21:25:58
○ 2026-08-09 02:51:00
○A2606:4700:3035::ac43:dda82021-09-09 → 2021-09-09 · 4 obs
● 2021-09-09 21:25:58
○ 2026-02-26 19:21:48
○ 2026-08-09 02:51:00
○A2606:4700:3036::6815:33382021-09-09 → 2021-09-09 · 4 obs
● 2021-09-09 21:25:58
○ 2026-02-26 19:21:48
○ 2026-08-09 02:51:00
●A51.158.210.1082026-02-26 → 2026-08-09 · 3 obs
● 2026-02-26 19:21:48
● 2026-08-09 02:51:00
○A95.141.32.252015-07-09 → 2015-07-09 · 3 obs
○ 2015-09-27 23:03:20
○ 2026-08-09 02:51:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| me | a0.nic.me, a2.nic.me, b0.nic.me, b2.nic.me... | - |
| servermonitoring.me | jake.datasec.sh, kate.datasec.sh | - |
✅ Authoritative Response
Server:51.15.100.248
NS records: jake.datasec.sh, kate.datasec.sh
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for servermonitoring.me (unsigned zone)
⏱️ Timing
Total: 752ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 51.158.210.108 |
| NS | 2 | jake.datasec.sh, kate.datasec.sh |
| SOA | 1 | jake.datasec.sh dns.datasec.sh |
Analysis
IP Addresses
servermonitoring.me has exactly one IP address — 51.158.210.108.
Other host names share IP numbers with servermonitoring.me; 51-158-210-108.lb.nl-ams.scw.cloud is one such example.
Name Servers
servermonitoring.me is served by two delegated name servers, jake.datasec.sh and kate.datasec.sh.
servermonitoring.me shares the same name server configuration with sethealth.ru, spaceyes3d.ru, rubysoft.ru and coworkingrussia.com.
jake.datasec.sh and kate.datasec.sh each resolve to one IP number: jake.datasec.sh points to 51.158.190.33 and kate.datasec.sh points to 51.15.100.248.