venezlo-pl.shop
“404 Not Found”
Evidence Summary
PhishDestroy first observed venezlo-pl.shop on Sep 19, 2026. Stored content metadata identifies Unknown as the apparent target. The captured page title is “404 Not Found”. Current evidence score: 100/100 (critical).
Positive findings are stored from 2 sources: VirusTotal and Spamhaus DBL. VirusTotal recorded 16 detections among 89 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, SOCRadar, Sophos, VIPRE, Webroot on Sep 20, 2026 at 14:24 UTC. Spamhaus DBL: DBL_PHISH on Sep 19, 2026 at 22:30 UTC. Non-positive and contextual checks: AlienVault OTX listed 5 community pulse references (not vendor detections) on Sep 20, 2026 at 14:25 UTC. The separate external-blocklist snapshot contained no matches on Sep 20, 2026 at 14:20 UTC. Google Safe Browsing returned no flag on Sep 20, 2026 at 14:24 UTC. URLScan completed without a malicious verdict (score 0) on Sep 20, 2026 at 03:30 UTC.
HTTP 200 was recorded on Sep 20, 2026 at 10:00 UTC. At collection time, the hostname resolved to 43.130.0.66 on AS132203 (Tencent Building, Kejizhongyi Avenue). The recorded endpoint location is Santa Clara, US. The stored server header is nginx. DOM analysis on Sep 19, 2026 at 22:20 UTC returned 98/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / R13 as the certificate issuer with validity through Jun 3, 2026; checked Sep 19, 2026 at 22:02 UTC.
The content indicators and 2 positive source findings support the current Unknown impersonation and phishing classification. The target field identifies Unknown, but the record does not establish whether the page requested credentials, a seed phrase, or a wallet connection.
Forensic History & Detection Timeline
-
Threat First Observed Sep 19, 2026 · 23:56 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
43.130.0.66.
Threat Response Pipeline
Public Blocklist Status
Evasion analysis
Cloaking suspected: scanner and victim titles differ
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
- Server header seen by scanner
nginx
Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx
VirusTotal Analysis
Evidence & External Reports
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive