The domain investwfg.org was observed with a PhishDestroy listing on 2026-10-13, and its network performance was measured with a PageSpeed score of 52. It was also referenced on two external blocklists during this period.
Recorded Evidence
On 2026-10-13, investwfg.org appeared on both the MetaMask and SEAL external blocklists. The domain was first observed on 2026-10-13 and registered through Gname.com Pte. Ltd. on 2026-09-22. VirusTotal checked the domain on 2026-10-01, recording zero detections out of 92 scanners. OTX pulses referenced the domain once as of 2026-10-13. The domain’s PageSpeed performance score was recorded as 52 on 2026-10-13.
Interpretation
PhishDestroy contains a listing for investwfg.org, documenting its presence in a security context. VirusTotal’s record provides a snapshot of how many scanners detected issues with the domain, while OTX pulses reflect community intelligence and references. These sources cover a range of technical and threat intelligence checks, offering a multi-faceted view of the domain’s profile as of the recorded dates.
Recommended Actions
For investwfg.org, retain the PhishDestroy, VirusTotal, and OTX records as reference points for ongoing monitoring. Compare future blocklist entries and detection results with these stored observations to track any changes in the domain’s security profile. Consult the external blocklist entries for updates relevant to network filtering or risk assessments.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-13 10:00:12 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:00:12 UTClast content: 2026-10-13 10:00:12 UTC
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.
使用技術 · 5 identified
V
Vue.js
JavaScript frameworks
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of investwfg.org· checked Oct 13, 2026
52
Needs Work
Performance
FCP
10.61s
First Contentful Paint
LCP
13.69s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
197ms
Total Blocking Time
SI
12.56s
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:06 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
ブロックリストの検出
掲載先 2 blocklists: MetaMask, SEAL
2026年10月13日
OTX Community References
1 community publication reference on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Brand Impersonation
Impersonation of Across
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(SG)
