securitycams.com - dns.ninja
securitycams.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 216.150.1.1🇨🇦 Amazon216.150.1.0/24 EC2 Prefix | ||||||
| A | 216.150.16.129🇨🇦 Amazon216.150.16.0/24 EC2 Prefix | ||||||
| NS | ns1.vercel-dns.com ⭐ | ||||||
| A | 2620:4d:4000:6259:7:13:0:1🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1 | ||||||
| PTR | dns1.p13.nsone.net | ||||||
| A | 198.51.44.13🇺🇸 NSONE198.51.44.0/24 | ||||||
| PTR | dns1.p13.nsone.net | ||||||
| NS | ns2.vercel-dns.com | ||||||
| A | 2a00:edc0:6259:7:13::2🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2 | ||||||
| PTR | dns2.p13.nsone.net | ||||||
| A | 198.51.45.13🇺🇸 NSONE198.51.45.0/24 | ||||||
| PTR | dns2.p13.nsone.net | ||||||
| SOA | ns1.vercel-dns.comhostmaster@nsone.net serial=1725567578 | ||||||
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=1786400044 | ||||||
Same first word
securitycams.ca |
securitycams.com.au |
securitycams.us |
securitycams.ch |
securitycams.de |
securitycams.shop |
securitycams.com |
Similar names
camssecurity.com.au |
camssecurity.com |
securityscam.org |
casmsecurity.com |
camssecurity.co.uk |
securityscam.com |
scamsecurity.com |
DNS History
16 records (4 active, 12 former)
○NSbuy.internettraffic.com2015-07-01 → 2016-04-16 · 4 obs
● 2015-07-01 03:21:10
● 2016-04-16 20:37:28
○ 2016-11-30 00:50:18
○ 2026-08-10 22:32:12
● 2016-04-16 20:37:28
○ 2016-11-30 00:50:18
○ 2026-08-10 22:32:12
○NSns1.uniregistrymarket.link2016-11-30 → 2017-07-04 · 5 obs
○ 2016-04-16 20:37:28
● 2016-11-30 00:50:18
● 2017-07-04 04:58:50
○ 2026-03-03 13:10:58
○ 2026-08-10 22:32:12
● 2016-11-30 00:50:18
● 2017-07-04 04:58:50
○ 2026-03-03 13:10:58
○ 2026-08-10 22:32:12
●NSns1.vercel-dns.com2026-03-03 → 2026-08-10 · 3 obs
○ 2017-07-04 04:58:50
● 2026-03-03 13:10:58
● 2026-08-10 22:32:12
● 2026-03-03 13:10:58
● 2026-08-10 22:32:12
○NSns2.uniregistrymarket.link2016-11-30 → 2017-07-04 · 5 obs
○ 2016-04-16 20:37:28
● 2016-11-30 00:50:18
● 2017-07-04 04:58:50
○ 2026-03-03 13:10:58
○ 2026-08-10 22:32:12
● 2016-11-30 00:50:18
● 2017-07-04 04:58:50
○ 2026-03-03 13:10:58
○ 2026-08-10 22:32:12
●NSns2.vercel-dns.com2026-03-03 → 2026-08-10 · 3 obs
○ 2017-07-04 04:58:50
● 2026-03-03 13:10:58
● 2026-08-10 22:32:12
● 2026-03-03 13:10:58
● 2026-08-10 22:32:12
○NSsell.internettraffic.com2015-07-01 → 2016-04-16 · 4 obs
● 2015-07-01 03:21:10
● 2016-04-16 20:37:28
○ 2016-11-30 00:50:18
○ 2026-08-10 22:32:12
● 2016-04-16 20:37:28
○ 2016-11-30 00:50:18
○ 2026-08-10 22:32:12
●A216.150.1.12026-03-26 → 2026-08-10 · 7 obs
○ 2026-03-17 09:00:24
● 2026-03-26 07:44:28
○ 2026-03-29 15:55:48
● 2026-03-30 23:08:30
○ 2026-03-31 09:56:36
○ 2026-04-26 09:10:58
● 2026-08-10 22:32:12
● 2026-03-26 07:44:28
○ 2026-03-29 15:55:48
● 2026-03-30 23:08:30
○ 2026-03-31 09:56:36
○ 2026-04-26 09:10:58
● 2026-08-10 22:32:12
○A216.150.1.1292026-03-29 → 2026-03-31 · 7 obs
○ 2026-03-03 13:10:58
○ 2026-03-26 07:44:28
● 2026-03-29 15:55:48
○ 2026-03-30 23:08:30
● 2026-03-31 09:56:36
○ 2026-03-31 10:47:44
○ 2026-08-10 22:32:12
○ 2026-03-26 07:44:28
● 2026-03-29 15:55:48
○ 2026-03-30 23:08:30
● 2026-03-31 09:56:36
○ 2026-03-31 10:47:44
○ 2026-08-10 22:32:12
○A216.150.1.1932026-03-03 → 2026-03-26 · 7 obs
○ 2017-07-04 04:58:50
● 2026-03-03 13:10:58
○ 2026-03-07 17:20:36
○ 2026-03-17 09:00:24
● 2026-03-26 07:44:28
○ 2026-03-29 15:55:48
○ 2026-08-10 22:32:12
● 2026-03-03 13:10:58
○ 2026-03-07 17:20:36
○ 2026-03-17 09:00:24
● 2026-03-26 07:44:28
○ 2026-03-29 15:55:48
○ 2026-08-10 22:32:12
○A216.150.1.652026-03-17 → 2026-03-17 · 5 obs
○ 2026-03-03 13:10:58
○ 2026-03-07 17:20:36
● 2026-03-17 09:00:24
○ 2026-03-26 07:44:28
○ 2026-08-10 22:32:12
○ 2026-03-07 17:20:36
● 2026-03-17 09:00:24
○ 2026-03-26 07:44:28
○ 2026-08-10 22:32:12
○A216.150.16.12026-03-07 → 2026-04-26 · 9 obs
○ 2026-03-03 13:10:58
● 2026-03-07 17:20:36
○ 2026-03-17 09:00:24
○ 2026-03-26 07:44:28
● 2026-03-29 15:55:48
● 2026-03-31 09:56:36
○ 2026-03-31 10:47:44
● 2026-04-26 09:10:58
○ 2026-08-10 22:32:12
● 2026-03-07 17:20:36
○ 2026-03-17 09:00:24
○ 2026-03-26 07:44:28
● 2026-03-29 15:55:48
● 2026-03-31 09:56:36
○ 2026-03-31 10:47:44
● 2026-04-26 09:10:58
○ 2026-08-10 22:32:12
●A216.150.16.1292026-03-07 → 2026-08-10 · 5 obs
○ 2026-03-03 13:10:58
● 2026-03-07 17:20:36
○ 2026-03-17 09:00:24
○ 2026-04-26 09:10:58
● 2026-08-10 22:32:12
● 2026-03-07 17:20:36
○ 2026-03-17 09:00:24
○ 2026-04-26 09:10:58
● 2026-08-10 22:32:12
○A216.150.16.1932026-03-17 → 2026-04-26 · 7 obs
○ 2026-03-07 17:20:36
● 2026-03-17 09:00:24
○ 2026-03-26 07:44:28
○ 2026-03-31 09:56:36
● 2026-03-31 10:47:44
● 2026-04-26 09:10:58
○ 2026-08-10 22:32:12
● 2026-03-17 09:00:24
○ 2026-03-26 07:44:28
○ 2026-03-31 09:56:36
● 2026-03-31 10:47:44
● 2026-04-26 09:10:58
○ 2026-08-10 22:32:12
○A216.150.16.652026-03-03 → 2026-03-31 · 7 obs
○ 2017-07-04 04:58:50
● 2026-03-03 13:10:58
○ 2026-03-07 17:20:36
○ 2026-03-31 09:56:36
● 2026-03-31 10:47:44
○ 2026-04-26 09:10:58
○ 2026-08-10 22:32:12
● 2026-03-03 13:10:58
○ 2026-03-07 17:20:36
○ 2026-03-31 09:56:36
● 2026-03-31 10:47:44
○ 2026-04-26 09:10:58
○ 2026-08-10 22:32:12
○A69.172.201.1532016-04-16 → 2017-07-04 · 5 obs
○ 2016-01-29 02:32:34
● 2016-04-16 20:37:28
● 2017-07-04 04:58:50
○ 2026-03-03 13:10:58
○ 2026-08-10 22:32:12
● 2016-04-16 20:37:28
● 2017-07-04 04:58:50
○ 2026-03-03 13:10:58
○ 2026-08-10 22:32:12
○A69.172.201.2082015-07-01 → 2016-01-29 · 4 obs
● 2015-07-01 03:21:10
● 2016-01-29 02:32:34
○ 2016-04-16 20:37:28
○ 2026-08-10 22:32:12
● 2016-01-29 02:32:34
○ 2016-04-16 20:37:28
○ 2026-08-10 22:32:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| securitycams.com | ns1.vercel-dns.com, ns2.vercel-dns.com | 4 records |
✅ Authoritative Response
Server:198.51.44.13
NS records: ns1.vercel-dns.com, ns2.vercel-dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for securitycams.com (unsigned zone)
⏱️ Timing
Total: 215ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 216.150.1.65, 216.150.1.193 |
| NS | 2 | ns1.vercel-dns.com, ns2.vercel-dns.com |
| SOA | 1 | ns1.vercel-dns.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.vercel-dns.com, ns1.vercel-dns.com, ns2.vercel-dns.com...)
Analysis
IP Addresses
securitycams.com points to the IP addresses 216.150.1.1 and 216.150.16.129
Two other host names, along with eqscout.com, armwrestling.or.kr and coflow.com.tr, also share IP numbers with securitycams.com.
Name Servers
securitycams.com is delegated to two name servers: ns1.vercel-dns.com and ns2.vercel-dns.com.
securitycams.com shares its NS records with other domains, for example velocitydm.com, scholarquest.com.np, avanzen.ai and two others.
securitycams.com shares at least some of its name servers with other domains, such as socialswish.com.
ns1.vercel-dns.com and ns2.vercel-dns.com each resolve to two IP addresses: ns1.vercel-dns.com points to 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1, while ns2.vercel-dns.com points to 198.51.45.13 and 2a00:edc0:6259:7:13::2.