trust-wallets.company was recorded on two external blocklists, MetaMask and SEAL, as of 2026-10-13, and also received a PageSpeed performance score of 100 on that date. The domain was additionally referenced in multiple security intelligence sources during the same observation period.
Recorded Evidence
On 2026-10-13, trust-wallets.company appeared on the MetaMask and SEAL blocklists. VirusTotal checked the domain on 2026-10-10, reporting 0 detections out of 92 scanners. OTX pulses included two entries for the domain as of 2026-10-13. PhishDestroy internally listed trust-wallets.company on 2026-10-13. The domain was registered through Name.com, Inc. on 2026-10-10.
Interpretation
PhishDestroy’s internal listing documents trust-wallets.company as present in its system, providing a record of its status for that date. VirusTotal’s measurement contains the results of its detection scan, reporting the number of security engines that flagged the domain. The OTX record logs pulse entries, which are used to track intelligence references over time. These sources together offer a multi-faceted view of how trust-wallets.company was referenced in security and technical intelligence feeds on their respective dates.
Recommended Actions
Monitor trust-wallets.company using records from MetaMask, SEAL, VirusTotal, and PhishDestroy to track changes in security listings. Preserve OTX pulse entries and the PageSpeed performance score for future comparison. Compare new findings from these sources to the existing records to maintain an up-to-date security profile for trust-wallets.company.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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 trust-wallets.company· checked Oct 13, 2026
100
Good
Performance
FCP
1.54s
First Contentful Paint
LCP
1.54s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.54s
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:27:58 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 216.198.79.65.
威胁响应 Pipeline
发现
Analysis
Monitoring
8 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
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Brand Impersonation
Impersonation of Trust Wallet
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.
(SE)
