VirusTotal
6 / 91 engine detections
レポートを開く“TrustWallet — Pay”
Security analysis of trustserveruae.network covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 91 engine detections
レポートを開くchecked — no match recorded
24 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
trustserveruae.network was registered on March 07, 2026 through NameCheap, Inc. The domain resolves to IP 104.21.28.104, which belongs to AS13335 Cloudflare, Inc., located in the United States. The site presents an SSL certificate issued by Let’s Encrypt (E7), indicating use of a free TLS service. The domain’s MX records point to mx1-hosting.jellyfish.systems (priority 5) and a secondary host with priority 10, suggesting reliance on third‑party mail infrastructure.
The web server returns an HTTP 302 redirect and serves a page titled “TrustWallet — Pay”, directly impersonating the TrustWallet brand. Technology fingerprints include Cloudflare Browser Insights, Cloudflare, and HTTP/3, confirming the front‑end is protected by Cloudflare’s edge network. VirusTotal reports a single positive out of 95 security vendors, and the domain appears on one external blocklist, indicating limited but existing detection.
Current intelligence classifies the campaign as a seed phishing operation targeting TrustWallet users. The low detection count and single blocklist listing suggest the campaign may be newly deployed or operating under the radar of many scanning services. The presence of Cloudflare’s DNS (kirk.ns.cloudflare.com, maya.ns.cloudflare.com) masks the origin of the backend server, leaving the ultimate hosting environment uncertain.
Defenders should add trustserveruae.network to network deny lists and configure DNS filtering to block resolution. Monitoring of outbound connections to 104.21.28.104 and the associated Cloudflare nameservers can provide early indicators of compromised clients attempting to contact the site. Incident response teams should alert users of TrustWallet to verify any payment requests against official channels, and threat‑intelligence feeds should be updated to include the domain’s IP and MX hosts for broader correlation.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x1f7b10070F1b7766F585D7DdeaF62f88B55A7d83Format validated · Domain analysisIoC extraction recorded 2026-07-29 02:26:46 UTC
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.
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.
Edge-IP の評判はこのドメインに起因しません。
maya.ns.cloudflare.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
9c8ed96079f1b404bb8a23c2b689492265c8ce21831f348ba9911afa65270463Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of trustserveruae.network · checked Mar 8, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_302; http=302; via=https_proxy; location=https://trustserveruae.network/cgi-sys/suspendedpage.cgi; server=cloudflare
trustserveruae.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
live_content→redirected
http_redirect
redirected→live_content
content_served
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
3→4
1→3
0→1
https://radar.cloudflare.com/scan/bd9f47bb-ffad-4516-8723-ccf5f60781c1
No threat flag
View source24 community references
View source6/91 engine detections
View sourcePage captured
View sourcetrustserveruae.network
View source保存された類似ドメイン:104 件
104 件中 100 件を表示
コミュニティの 1 人が報告・初回確認 2026年3月7日
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
trustserveruae.network)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.