TrustWalletPay.cloud was externally blocked by MetaMask and SEAL as of 2026-10-11, per dated observation. The domain was also listed internally by PhishDestroy, which is a distinct indicator from external blocklists.
Recorded Evidence
MetaMask and SEAL both recorded trustwalletpay.cloud on their external blocklists as of 2026-10-11. The domain was first observed on 2026-10-11 and internally listed by PhishDestroy on the same date. Its registration was recorded with HOSTINGER operations, UAB on 2026-10-09, and its SSL certificate was issued by Let's Encrypt / YR1.
Interpretation
PhishDestroy contains an internal listing for trustwalletpay.cloud, which is a measurement of its own internal assessment. External blocklists such as MetaMask and SEAL provide records of detection, each documenting their own criteria and scope. The timeline shows that these observations were made within a close range of dates, allowing for comparison of how quickly different sources recorded the domain.
Recommended Actions
For trustwalletpay.cloud, preserve the blocklist entries from MetaMask and SEAL as distinct records for ongoing reference. Compare the internal listing from PhishDestroy with external blocklist records to track any future changes or additional entries. Maintain a record of the registration and SSL certificate details for technical context in future assessments.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='trustwalletpay.cloud', port=80): Max retries exceeded with url: / (Caused by NewConnection
DOM Analysisanalyzed 2026年10月11日score 15/1001 brand signal
Submitted URLhttp://trustwalletpay.cloud/
Favicon Hash
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 11:02:13 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 09:51:53 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.
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-11 09:51:53 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 173.208.142.58.
威胁响应 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.
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.
(LT)
