sysmonitorweb.dev - dns.ninja
sysmonitorweb.dev
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
sysmonitorweb.dev |
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A77.113.182.482026-10-12 → 2026-11-12 · 2 obs
● 2026-11-12 12:32:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com... | - |
| sysmonitorweb.dev | ns4cfn.name.com, ns3cfp.name.com, ns2hjl.name.com, ns1bqx.name.com | - |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns4cfn.name.com, ns3cfp.name.com, ns2hjl.name.com, ns1bqx.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sysmonitorweb.dev (unsigned zone)
⏱️ Timing
Total: 779ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 77.113.182.48 |
| NS | 4 | ns1bqx.name.com, ns2hjl.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
sysmonitorweb.dev has exactly one IP address — 77.113.182.48.
Name Servers
Five name servers handle delegation for sysmonitorweb.dev: ns1.name.com, ns1bqx.name.com, ns2hjl.name.com and two others.
sysmonitorweb.dev has at least partial name server overlap with other domains, such as pepssentialsplus.com, palinatolma.ch, texasveteransassist.net and two others.
ns4cfn.name.com, ns3cfp.name.com and ns2fln.name.com — plus 7 other name servers — are commonly paired with these name servers.
Host names pointing to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1bqx.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2hjl.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3cfp.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4cfn.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1bqx.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1bqx.name.com resolve to 163.114.216.17 IP addresses each.