exocams.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked13 years old
20
exocams.com was registered on 24 May 2013 via NameCheap, Inc. and the registry expiry is 24 May 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/exocams.com.
exocams.com publishes 2 nameservers. DNSSEC is not signed.
exocams.com has 2 IPv4 addresses (192.64.119.100, 35.190.1.20). The geolocation database places 192.64.119.100 in Dallas, United States.
Domain · RDAP/WHOIS
exocams.com was registered on 24 May 2013 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/exocams.com.
| Registered | since 24 May 2013 |
|---|---|
| Created | 24 May 2013 |
| Updated | 2 May 2025 |
| Expires | 24 May 2028 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | dns1.registrar-servers.com, dns2.registrar-servers.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/exocams.com |
exocams.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver dns1.registrar-servers.com is published for exocams.com in the registration record from https://rdap.verisign.com/com/v1/domain/exocams.com.
Nameserver dns2.registrar-servers.com is published for exocams.com in the registration record from https://rdap.verisign.com/com/v1/domain/exocams.com.
DNS
exocams.com has 2 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 192.64.119.100, 35.190.1.20 |
|---|---|
| AAAA | — |
| NS | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | eforward1.registrar-servers.com (10), eforward2.registrar-servers.com (10), eforward3.registrar-servers.com (10), eforward4.registrar-servers.com (15), eforward5.registrar-servers.com (20) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at exocams.com is "v=spf1 include:spf.efwd.registrar-servers.com ~all".
IPv4 address 192.64.119.100 answers for exocams.com at resolver 1.1.1.1:53.
IPv4 address 35.190.1.20 answers for exocams.com at resolver 1.1.1.1:53.
Mail exchanger eforward1.registrar-servers.com has preference 10.
Mail exchanger eforward2.registrar-servers.com has preference 10.
Mail exchanger eforward3.registrar-servers.com has preference 10.
Mail exchanger eforward4.registrar-servers.com has preference 15.
Mail exchanger eforward5.registrar-servers.com has preference 20.
Hosting and geo
exocams.com is placed in Dallas, United States by the local geolocation database (db-ip).
| Address | 192.64.119.100 |
|---|---|
| Country | United States |
| City | Dallas |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for exocams.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
EOF
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://exocams.com/": EOF
Security
Family DNS for exocams.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for exocams.com. That resolver covers adult and malware names.
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Dallas.
- October 2026: geo country changed from empty to United States.
Questions
Is exocams.com safe?
Cloudflare family DNS returned a block for exocams.com. That resolver covers adult and malware names.
Who hosts exocams.com?
exocams.com is placed in Dallas, United States.
When does exocams.com expire?
exocams.com expires on 24 May 2028 according to https://rdap.verisign.com/com/v1/domain/exocams.com.
Who owns exocams.com?
The registry did not return a person or a company for exocams.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/exocams.com at 2026-10-30T13:53:36Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:53:36Z
- TLS source tls:443 at 2026-10-30T13:53:36Z
- HTTP source https://exocams.com/ at 2026-10-30T13:53:36Z
- Tech source not available at 2026-10-30T13:53:36Z
- Geo source db-ip at 2026-10-30T13:53:36Z
- Safety source family DNS and local lists at 2026-10-30T13:53:36Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.