VirusTotal
5 / 92
On 2026-10-08 the domain otc-holder.com returned an HTTP 403 status code, indicating restricted access during that observation. The domain was also listed on two external blocklists, MetaMask and SEAL, as of the same date.
OTX recorded 3 pulses on 2026-10-08. VirusTotal detected 5 detections out of 92 scanners on 2026-10-02. The domain was first observed on 2026-10-07 and was internally listed by Phishdestroy. The registrar is NICENIC INTERNATIONAL GROUP CO., LIMITED, and the SSL certificate was issued by Let's Encrypt / YE1, scanned on 2026-10-08.
These dated observations show how otc-holder.com was evaluated across multiple platforms within days of its registration. The HTTP 403 response documents a specific access restriction, while the blocklist entries and OTX pulses reflect external monitoring interest. VirusTotal’s detections and Phishdestroy’s internal listing indicate cross-source scrutiny during the same period.
Review the blocklist records from MetaMask and SEAL for otc-holder.com, and compare them with VirusTotal’s detection results and OTX pulses. Preserve the HTTP 403 response and the internal Phishdestroy listing for reference. Track future changes in these records to monitor any shifts in the domain’s status.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='otc-holder.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Edge-IP reputation is not attributed to this domain.
leanna.ns.cloudflare.comLocation describes the IP network.
c1ccffb6b63fb8dbe8f43907bf606c209f2f8e6a2b4a62a08d8209ae72fce1c4Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of otc-holder.com · checked Oct 7, 2026
188.114.97.1. 11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
79 stored lookalike domains
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive