securecop.com - dns.ninja
securecop.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=1784949922 | ||||||
Same first word
securecop.com |
Similar names
DNS History
7 records (6 active, 1 former)
βNSns1.name.com2026-06-30 β 2026-07-25 Β· 3 obs
β 2017-07-21 03:17:38
β 2026-06-30 18:58:12
β 2026-07-25 03:48:04
β 2026-06-30 18:58:12
β 2026-07-25 03:48:04
βNSns1dhl.name.com2017-07-21 β 2026-07-25 Β· 2 obs
β 2017-07-21 03:17:38
β 2026-07-25 03:48:04
β 2026-07-25 03:48:04
βNSns2jrt.name.com2017-07-21 β 2026-07-25 Β· 2 obs
β 2017-07-21 03:17:38
β 2026-07-25 03:48:04
β 2026-07-25 03:48:04
βNSns3dkz.name.com2017-07-21 β 2026-07-25 Β· 2 obs
β 2017-07-21 03:17:38
β 2026-07-25 03:48:04
β 2026-07-25 03:48:04
βNSns4fmw.name.com2017-07-21 β 2026-07-25 Β· 2 obs
β 2017-07-21 03:17:38
β 2026-07-25 03:48:04
β 2026-07-25 03:48:04
βA69.64.147.2422015-09-02 β 2017-07-21 Β· 4 obs
β 2015-09-02 00:13:38
β 2017-07-21 03:17:38
β 2026-06-30 18:58:12
β 2026-07-25 03:48:04
β 2017-07-21 03:17:38
β 2026-06-30 18:58:12
β 2026-07-25 03:48:04
βA91.195.240.822026-06-30 β 2026-07-25 Β· 3 obs
β 2017-07-21 03:17:38
β 2026-06-30 18:58:12
β 2026-07-25 03:48:04
β 2026-06-30 18:58:12
β 2026-07-25 03:48:04
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| securecop.com | ns1dhl.name.com, ns2jrt.name.com, ns3dkz.name.com, ns4fmw.name.com | 8 records |
β Authoritative Response
Server:163.114.216.17
NS records: ns1dhl.name.com, ns2jrt.name.com, ns3dkz.name.com, ns4fmw.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for securecop.com (unsigned zone)
β±οΈ Timing
Total: 4867ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.82 |
| NS | 4 | ns1dhl.name.com, ns2jrt.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1dhl.name.com, ns1dhl.name.com, ns2jrt.name.com...)
Analysis
IP Addresses
securecop.com resolves to one IP address: 91.195.240.82.
Name Servers
securecop.com has five name servers, which are ns1.name.com, ns1dhl.name.com, ns2jrt.name.com and two others.
ns1.name.com and ns3dkz.name.com each resolve to two IP addresses: ns1.name.com points to 163.114.216.17 and 2a00:edc0:107::1, while ns3dkz.name.com points to 163.114.217.17 and 2a00:edc0:107::49.