The domain investwfg.net was recorded with an HTTP status 200 on 2026-10-13, documenting a successful response at that time. On the same date, investwfg.net was listed on two external blocklists, highlighting entries in MetaMask and SEAL.
Recorded Evidence
On 2026-10-13, VirusTotal recorded 0 detections out of 92 scanners for investwfg.net. OTX documented two threat intelligence pulses on the same date. PhishDestroy included an internal listing for the domain, and the SSL certificate was issued by Let's Encrypt / YE2. The domain was registered with Gname.com Pte. Ltd. on 2026-04-03.
Interpretation
The PhishDestroy internal listing provides a recorded security context for investwfg.net, while VirusTotal’s scan measures file-level detection results from multiple scanners. OTX records document community-sourced intelligence pulses, and the HTTP status observation captures the domain’s technical response on the recorded date. These sources collectively offer a multi-faceted snapshot of the domain’s status and external references as of 2026-10-13.
Recommended Actions
Preserve the VirusTotal and OTX records for investwfg.net to enable future comparison of detection and intelligence pulse changes. Review the external blocklist entries from MetaMask and SEAL for updates or removals over time. Retain the HTTP status 200 record as a technical reference point for subsequent connectivity checks.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Google PageSpeed Insights — mobile performance audit of investwfg.net· checked Oct 13, 2026
50
Needs Work
Performance
FCP
10.99s
First Contentful Paint
LCP
13.36s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
287ms
Total Blocking Time
SI
11.19s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-12 23:43:04 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.33.3.
Threat Response Pipeline
Discovery
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
investwfg.net detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 13, 2026
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 13, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
3 evidence signal groups linked0 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
(SG)
