VirusTotal
2 / 91 engine detections
レポートを開く“Send BNB | Trust Wallet”
ブロックリスト掲載ドメイン: bnb20.network — コンテンツが利用できません. 証拠の概要: VirusTotal 2/91 (Forcepoint ThreatSeeker, Gridinsoft); URLQuery 1 alert; PhishDestroy score 71/100.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 91 engine detections
レポートを開く1 threat-system alert
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | bnb20.network |
malicious | Sinkholed |
PhishDestroy threat report
Analysis of the domain bnb20.network indicates it is a confirmed phishing site targeting users of a cryptocurrency platform, with elevated risk due to its infrastructure and detection status. The domain was registered on March 6, 2026, through NameCheap, Inc., and resolves to the IP address 3.174.46.33, hosted on Amazon Web Services (AS16509) in Germany. The SSL certificate is issued by Amazon RSA 2048 M04, a common provider for both legitimate and malicious sites, offering no inherent trust signals beyond basic encryption. Detection data reveals limited but actionable intelligence: the domain appears on one security blocklist (PhishDestroy) and is flagged by 2 of 91 security vendors on VirusTotal, suggesting early but growing recognition as malicious.
Gridinsoft assigns a trust score of 0/100, reinforcing its classification as high-risk. No additional details about the phishing kit, page content, or specific brand impersonation are available in the provided data, though the domain name suggests a likely association with Binance or a related cryptocurrency service. Defenders should treat this domain as actively malicious based on its registration context, hosting provider, and detection status. The use of NameCheap for registration and AWS for hosting is consistent with phishing campaigns due to the accessibility and scalability of these services.
While the domain is currently offline, historical resolutions and SSL certificates may still pose risks for retrospective analysis or incident response. Organizations are advised to block the domain at the DNS or proxy level, monitor for related infrastructure (e.g., shared IPs, nameservers), and review logs for connections to 3.174.46.33 or the domain itself. Further investigation into the phishing kit or payload is recommended if additional artifacts, such as HTTP headers or page titles, become available.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0xccD642c9acb072F72F29b77E422f5c024ecF5cBaFormat validated · Domain analysisIoC extraction recorded 2026-07-29 02:51: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.
ns-1194.awsdns-21.orgns-1720.awsdns-23.co.ukns-87.awsdns-10.comns-994.awsdns-60.netLocation describes the IP network.
2e8cf93b442cb894f3bc52d32fd55f3170fc573c7e64f3f8afada943fba5386fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bnb20.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
bnb20.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
2/91 engine detections
View sourceNo threat flag
View sourcePD-20260624-EB1D69
bnb20.network
View sourcePage captured
View sourcePD-20260624-EB1D69 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
bnb20.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.