lens-method.com
“404 Not Found”
Evidence Summary
PhishDestroy first observed lens-method.com on Sep 18, 2026. Stored content metadata identifies Unknown as the apparent target. The captured page title is “404 Not Found”. Stored page analysis classifies the content as impersonation. Current evidence score: 95/100 (critical).
One source contains a positive finding: VirusTotal. VirusTotal recorded 15 detections among 89 engines: alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot on Sep 19, 2026 at 20:53 UTC. Non-positive and contextual checks: On Sep 19, 2026 at 20:53 UTC, AlienVault OTX listed 3 community pulse references (not vendor detections); Google Safe Browsing returned no flag. The separate external-blocklist snapshot contained no matches on Sep 20, 2026 at 14:20 UTC. URLScan completed without a malicious verdict (score 0) on Sep 19, 2026 at 03:33 UTC.
No conclusive timestamped HTTP response is stored. Registration records for the domain list eNom, LLC as the registrar and Sep 1, 2021 as the creation date. At collection time, the hostname resolved to 167.71.76.147 on AS14061 (DigitalOcean, LLC). The recorded endpoint location is Amsterdam, NL. The stored server header is nginx/1.18.0 (Ubuntu). The evidence archive retains 1 visual capture from PhishDestroy. TLS metadata lists R12 as the certificate issuer.
Stored content provides classification context, but only one source contains a positive finding.
Forensic History & Detection Timeline
-
Threat First Observed Sep 18, 2026 · 22:38 UTCDomain ingestion complete. Initial state is marked as unknown pointing to IP
167.71.76.147.
Threat Response Pipeline
Public Blocklist Status
Evasion analysis
Cloaking & traffic-distribution check
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
Scanner note: timeout: raw=timeout; http=0; via=http_proxy; error=HTTPConnectionPool(host='194.116.250.146', port=6604): Read timed out. (read timeout=7)
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