trustcashless.com was recorded on 2026-10-14 with entries on the MetaMask and SEAL external blocklists, providing a dated reference for its security profile. This domain also received a PageSpeed performance score, adding a technical perspective to the available data.
Recorded Evidence
On 2026-10-14, trustcashless.com appeared on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on 2026-10-13, recording 0 detections out of 92 total scanners. The domain was listed internally by PhishDestroy as of 2026-10-14. A PageSpeed performance score of 96 was also recorded on 2026-10-14.
Interpretation
The VirusTotal record contains a measurement from a large set of security scanners, documenting the domain's detection status on a specific date. PhishDestroy's internal listing provides another perspective by recognizing the domain within its own security-focused records. The presence on MetaMask and SEAL blocklists expands the context of external monitoring, showing that multiple sources have referenced trustcashless.com in their listings.
Recommended Actions
For trustcashless.com, retain the MetaMask and SEAL blocklist records alongside the VirusTotal scan results for future comparison. Preserve the PhishDestroy internal listing and PageSpeed performance score to enable tracking of changes over time. These records should be maintained to support ongoing review of the domain’s security and technical profile.
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
Capture routing
Localarchived 2026-10-14 21:58:35 UTC
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-14 19:57:16 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-14 19:57:16 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.
Values retained by the collector; long values may be shortened during collection.
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-14 19:57:16 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 64.29.17.1.
Threat Response Pipeline
Discovery
Analysis
Notifications
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
trustcashless.com 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 14, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 14, 2026
Sent Report Recorded
Stored outgoing record associated with registrar NAMECHEAP INC, 2 abuse contacts
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.
4 evidence signal groups linked1 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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · trustcashless.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
