On 2026-10-13, finance-community.net was recorded by Google Safe Browsing as flagged for social engineering, and it was also listed on two external blocklists. A PageSpeed performance score was documented on the same date, reflecting additional technical characteristics for the domain.
Recorded Evidence
Google Safe Browsing flagged finance-community.net for social engineering on 2026-10-13. On that date, the domain appeared on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on 2026-10-12, recording 0 detections out of 92 total scanners. The registrar was listed as Global Domain Group LLC, with a registration date of 2026-10-11. PhishDestroy internally listed the domain as of 2026-10-13, and a PageSpeed performance score of 62 was also recorded on that date.
Interpretation
The PhishDestroy internal listing contains a record of finance-community.net in a dedicated monitoring system, documenting its presence for security review. VirusTotal’s measurement provides a scan-based assessment across numerous engines, recording no detections at the time of its check. These sources collectively document both blocklist status and technical performance, offering a broad snapshot of the domain from multiple perspectives within a short timeframe.
Recommended Actions
For finance-community.net, preserve the Google Safe Browsing and VirusTotal records for future reference and comparison. Review the MetaMask and SEAL blocklist entries to monitor any changes in external listings. Retain the PhishDestroy listing and PageSpeed performance score to support ongoing contextual analysis of the domain’s recorded history.
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.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 finance-community.net· checked Oct 13, 2026
62
Needs Work
Performance
FCP
3.16s
First Contentful Paint
LCP
7.36s
Largest Contentful Paint
CLS
0.173
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.16s
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.
Status Check2026-10-12 23:43:56 UTC
Telemetry event observed.
Threat First Observed2026-10-12 23:43:01 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.59.244.
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
finance-community.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.
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.
2 evidence signal groups linked0 reports recordedUnverified
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 →
(US)
