rdsecure.com - dns.ninja
rdsecure.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=1785980464 | ||||||
Same first word
Similar names
DNS History
10 records (6 active, 4 former)
●NSns1.name.com2026-03-24 → 2026-08-06 · 3 obs
● 2026-03-24 15:04:10
● 2026-08-06 02:02:20
○NSns1cwy.domainsite.com2015-05-19 → 2016-09-25 · 4 obs
● 2016-09-25 22:08:28
○ 2019-01-26 16:18:22
○ 2026-08-06 02:02:20
●NSns1cwy.name.com2019-01-26 → 2026-08-06 · 3 obs
● 2019-01-26 16:18:22
● 2026-08-06 02:02:20
○NSns2ckr.domainsite.com2015-05-19 → 2016-09-25 · 4 obs
● 2016-09-25 22:08:28
○ 2019-01-26 16:18:22
○ 2026-08-06 02:02:20
●NSns2ckr.name.com2019-01-26 → 2026-08-06 · 3 obs
● 2019-01-26 16:18:22
● 2026-08-06 02:02:20
○NSns3fhx.domainsite.com2015-05-19 → 2016-09-25 · 4 obs
● 2016-09-25 22:08:28
○ 2019-01-26 16:18:22
○ 2026-08-06 02:02:20
●NSns3fhx.name.com2019-01-26 → 2026-08-06 · 3 obs
● 2019-01-26 16:18:22
● 2026-08-06 02:02:20
○NSns4lqx.domainsite.com2015-05-19 → 2016-09-25 · 4 obs
● 2016-09-25 22:08:28
○ 2019-01-26 16:18:22
○ 2026-08-06 02:02:20
●NSns4lqx.name.com2019-01-26 → 2026-08-06 · 3 obs
● 2019-01-26 16:18:22
● 2026-08-06 02:02:20
●A208.90.215.1012015-05-19 → 2026-08-06 · 2 obs
● 2026-08-06 02:02:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| rdsecure.com | ns1cwy.name.com, ns2ckr.name.com, ns3fhx.name.com, ns4lqx.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1cwy.name.com, ns2ckr.name.com, ns3fhx.name.com, ns4lqx.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rdsecure.com (unsigned zone)
⏱️ Timing
Total: 422ms | 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 |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1cwy.name.com, ns1cwy.name.com, ns2ckr.name.com...)
Analysis
IP Addresses
rdsecure.com resolves to just one IP address, 208.90.215.101.
Among the host names that share IP numbers with rdsecure.com is rdsecure.net, as one example.
Name Servers
rdsecure.com delegates to five name servers: ns1.name.com, ns1cwy.name.com, ns2ckr.name.com and two others.
At least some of rdsecure.com's name servers are shared with other domains, for example a7elabs.com, 01xam.com, tjsg.net and two more.
These name servers tend to co-occur with ns3fhx.name.com, ns4lqx.name.com, ns4hny.name.com and 7 other name servers in the same DNS delegations.
Host names that have two IP addresses:
The A records for ns1.name.com return 163.114.216.17 and 2a00:edc0:107::1.
The A records for ns1cwy.name.com return 163.114.216.17 and 2a00:edc0:107::1.
The A records for ns2ckr.name.com return 163.114.216.49 and 2402:cf80:107::1.
The A records for ns3fhx.name.com return 163.114.217.17 and 2a00:edc0:107::49.
The A records for ns4lqx.name.com return 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com and ns1cwy.name.com each have 2a00:edc0:107::1 IP addresses.
ns1.name.com and ns1cwy.name.com each have 163.114.216.17 IP addresses.