rdsecure.net - dns.ninja
rdsecure.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=1786096069 | ||||||
Same first word
Similar names
DNS History
10 records (6 active, 4 former)
●NSns1.name.com2026-03-26 → 2026-08-07 · 3 obs
● 2026-03-26 11:28:02
● 2026-08-07 09:52:48
○NSns1cwy.domainsite.com2015-07-11 → 2016-06-24 · 4 obs
● 2016-06-24 09:27:46
○ 2017-08-18 00:53:26
○ 2026-08-07 09:52:48
●NSns1cwy.name.com2017-08-18 → 2026-08-07 · 3 obs
● 2017-08-18 00:53:26
● 2026-08-07 09:52:48
○NSns2ckr.domainsite.com2015-07-11 → 2016-06-24 · 4 obs
● 2016-06-24 09:27:46
○ 2017-08-18 00:53:26
○ 2026-08-07 09:52:48
●NSns2ckr.name.com2017-08-18 → 2026-08-07 · 3 obs
● 2017-08-18 00:53:26
● 2026-08-07 09:52:48
○NSns3fhx.domainsite.com2015-07-11 → 2016-06-24 · 4 obs
● 2016-06-24 09:27:46
○ 2017-08-18 00:53:26
○ 2026-08-07 09:52:48
●NSns3fhx.name.com2017-08-18 → 2026-08-07 · 3 obs
● 2017-08-18 00:53:26
● 2026-08-07 09:52:48
○NSns4lqx.domainsite.com2015-07-11 → 2016-06-24 · 4 obs
● 2016-06-24 09:27:46
○ 2017-08-18 00:53:26
○ 2026-08-07 09:52:48
●NSns4lqx.name.com2017-08-18 → 2026-08-07 · 3 obs
● 2017-08-18 00:53:26
● 2026-08-07 09:52:48
●A208.90.215.1012015-07-11 → 2026-08-07 · 2 obs
● 2026-08-07 09:52:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net... | - |
| rdsecure.net | ns1cwy.name.com, ns2ckr.name.com, ns3fhx.name.com, ns4lqx.name.com | - |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1cwy.name.com, ns2ckr.name.com, ns3fhx.name.com, ns4lqx.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rdsecure.net (unsigned zone)
⏱️ Timing
Total: 474ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 208.90.215.101 |
| NS | 4 | ns1cwy.name.com, ns2ckr.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
rdsecure.net has exactly one IP address — 208.90.215.101.
rdsecure.com is an example of another host name that shares IP numbers with rdsecure.net.
Name Servers
Five name servers handle delegation for rdsecure.net: ns1.name.com, ns1cwy.name.com, ns2ckr.name.com and two others.
rdsecure.net has at least partial name server overlap with other domains, such as metsabox.com, dokuzogluism.com, kenaze.com and two others.
ns3fhx.name.com, ns4lqx.name.com and ns4hny.name.com — plus 7 other name servers — are commonly paired with these name servers.
Host names pointing to two IP addresses:
ns1.name.com resolves to 163.114.216.17 and 2a00:edc0:107::1.
ns1cwy.name.com resolves to 163.114.216.17 and 2a00:edc0:107::1.
ns2ckr.name.com resolves to 163.114.216.49 and 2402:cf80:107::1.
ns3fhx.name.com resolves to 163.114.217.17 and 2a00:edc0:107::49.
ns4lqx.name.com resolves to 163.114.217.49 and 2402:cf80:107::49.
The host names ns1.name.com and ns1cwy.name.com both resolve to 2a00:edc0:107::1 IP addresses.
The host names ns1.name.com and ns1cwy.name.com both resolve to 163.114.216.17 IP addresses.