SSL certificate is invalid or expired. Issuer: WE1
证据摘要
关键
VirusTotal
6/93
URLScan
Stored capture
PhishDestroy identifies app-wallet-connect.network as a domain posing a specific brand impersonation threat, where attackers impersonate a well-known brand to deceive users.
The evidence of this threat is substantial, with 6 out of 95 VirusTotal security vendors flagging this domain, and it appears on 1 security blocklist, having been created on February 21, 2026, which suggests a relatively recent registration. The domain resolves to the IP address 104.21.69.47 and has an SSL certificate issued by WE1, which may give it a false sense of legitimacy.
If users have visited this domain, they should take immediate action to protect themselves, as the brand impersonation threat can lead to unintended consequences, such as financial loss or compromised sensitive information. Given that the domain is currently offline, it is crucial for users to remain vigilant and monitor their accounts for any suspicious activity, and to report any incidents to the relevant authorities to prevent further damage.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/walletconnectStored page reference
IoC extraction recorded 2026-08-01 04:30:53 UTC
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='app-wallet-connect.network', port=80): Max retries exceeded with url: / (Caused by NewConn
DOM Analysisanalyzed 2026年3月24日score 15/1001 brand signal
IoC Extractionscanned 2026年8月1日0 wallet · 1 Telegram IoC
页面标题
The WalletConnect Network: WCT Profile
Impersonates
Foundation
TLS 证书
Hostname coverage not recorded·
颁发者 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.69.47
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP 声誉不属于此域。
Location describes the IP network.
TLS 证书
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:12:41 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-03-30 19:36:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-30 19:36:15 UTC → 2026-09-30 16:14:55 UTC · 4,412.64hmidpoint estimate ≈ 2026-06-30 17:55:35 UTC · precision very low · basis bounded
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.
10 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.
