PhishDestroy first observed trust-chain-systems-eth-verify.network on Oct 13, 2026. The hostname uses “verify,” a pattern consistent with a account-verification lure; no target brand is confirmed from stored content. Current evidence score: 88/100 (critical).
Positive findings are stored from 4 sources: VirusTotal, MetaMask, SEAL, and URLQuery. VirusTotal recorded 1 detections among 92 engines: alphaMountain.ai on Oct 13, 2026 at 16:14 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 13, 2026 at 14:20 UTC. URLQuery recorded 3 detections; no observation timestamp was retained. Additional recorded evidence: AlienVault OTX listed 2 community pulse references (not vendor detections) on Oct 13, 2026 at 16:14 UTC. URLScan captured the page on Oct 13, 2026 at 15:47 UTC.
The collector marked the hostname reachable on Oct 13, 2026 at 15:47 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause stale current evidence on Oct 13, 2026 at 13:44 UTC. Registration records for the domain list Tucows Domains Inc. as the registrar and Oct 8, 2026 as the creation date. Registration preceded first observation by 5 days. At collection time, the hostname resolved to 216.198.79.1. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt / YR1 as the certificate issuer with validity through Jan 7, 2027; checked Oct 13, 2026 at 16:02 UTC.
The content indicators and 4 positive source findings support the current phishing classification.
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.
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-13 15:43:51 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.198.79.1.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
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.
(CA)
