securenext.org - dns.ninja
securenext.org
org
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a2.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | b0.org.afilias-nst.org | ||||||
| NS | b2.org.afilias-nst.org | ||||||
| NS | c0.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | d0.org.afilias-nst.org | ||||||
| SOA | a0.org.afilias-nst.infohostmaster@donuts.email serial=1786277892 | ||||||
Same first word
securenext.com |
securenext.in |
securenext.org |
securenext.net |
Similar names
xnetsecure.net |
nextsecure.ch |
netsecurex.com |
nextrescue.com |
netxsecure.com |
securenetx.org |
nextsecure.com |
nextsecure.org |
securenetx.digital |
DNS History
7 records (6 active, 1 former)
●NSns1.name.com2026-03-31 → 2026-08-09 · 3 obs
● 2026-03-31 10:14:22
● 2026-08-09 12:49:04
○A69.64.147.2422015-06-29 → 2017-07-03 · 4 obs
● 2017-07-03 12:29:08
○ 2020-02-19 14:21:26
○ 2026-08-09 12:49:04
●A91.195.240.822020-02-19 → 2026-08-09 · 3 obs
● 2020-02-19 14:21:26
● 2026-08-09 12:49:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| org | b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org | - |
| securenext.org | ns2fln.name.com, ns3cpr.name.com, ns4fmx.name.com, ns1fkl.name.com | - |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns2fln.name.com, ns3cpr.name.com, ns4fmx.name.com, ns1fkl.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for securenext.org (unsigned zone)
⏱️ Timing
Total: 563ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.82 |
| NS | 4 | ns1fkl.name.com, ns2fln.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
securenext.org resolves to just one IP address, 91.195.240.82.
Two other host names, along with threatteamsix.com, dccer.com and artis(0x616e616c)foodscrowdfunding.com, also share IP numbers with securenext.org.
Name Servers
securenext.org delegates to five name servers: ns1.name.com, ns1fkl.name.com, ns2fln.name.com and two others.
At least some of securenext.org's name servers are shared with other domains, for example dvyu.com, a1sign.com, istanbul-escorts.com and two more.
These name servers tend to co-occur with ns3cpr.name.com, ns4fmx.name.com, ns1hwy.name.com and 7 other name servers in the same DNS delegations.
Host names that have two IP addresses:
ns1.name.com maps to two IP addresses — 163.114.216.17 and 2a00:edc0:107::1.
ns1fkl.name.com maps to two IP addresses — 163.114.216.17 and 2a00:edc0:107::1.
ns2fln.name.com maps to two IP addresses — 163.114.216.49 and 2402:cf80:107::1.
ns3cpr.name.com maps to two IP addresses — 163.114.217.17 and 2a00:edc0:107::49.
ns4fmx.name.com maps to two IP addresses — 163.114.217.49 and 2402:cf80:107::49.
These two host names — ns1.name.com and ns1fkl.name.com — each point to 2a00:edc0:107::1 IP addresses.
These two host names — ns1.name.com and ns1fkl.name.com — each point to 163.114.216.17 IP addresses.