VirusTotal
11 / 91 engine detections
レポートを開く“Roundcube Webmail :: Bienvenido a Roundcube Webmail”
Coinbaseなりすまし: webmail.user-coinbase.support — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 11/91 (ChainPatrol, BitDefender, Chong Lua Dao, Forcepoint…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 91 engine detections
レポートを開くno 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
The domain webmail.user-coinbase.support was observed delivering a brand impersonation campaign targeting Coinbase. Infrastructure analysis shows the domain resolves to IP address 188.114.96.3, which belongs to AS13335 owned by Cloudflare, Inc., and is geolocated in the United States. The SSL certificate presented for the host is issued by Google Trust Services under the WE1 certificate authority, indicating the use of a legitimate certificate chain despite the malicious intent. HTTP requests to the site return a 403 status code, and the page title returned by the web server is "Roundcube Webmail :: Bienvenido a Roundcube Webmail," suggesting the presence of a Roundcube webmail interface, although the content has not been captured for further analysis.
The domain was registered through Cloudflare, Inc., and the hosting provider is identified as Cloudflare, employing HTTP/3 as part of its service stack. VirusTotal scanning recorded three detections out of ninety‑five security vendors, reflecting a modest but notable level of vendor consensus on malicious behavior. The domain appears on a single security blocklist and has been explicitly blocked by the PhishDestroy service. Current operational status is offline, with the site returning HTTP 403 and no active content visible.
Risk assessment classifies the threat as elevated due to the combination of brand impersonation, cryptocurrency‑related scam categorization, and partial vendor detection. Defensive recommendations include adding webmail.user-coinbase.support and its resolved IP 188.114.96.3 to network deny lists, monitoring for any future re‑registration attempts, and ensuring that endpoint protection solutions incorporate the observed vendor detections. Continuous observation of related threat‑intel feeds for new indicators tied to the Coinbase brand is advised.
For the registrable domain user-coinbase.support behind this subdomain, 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 の評判はこのドメインに起因しません。
Location describes the IP network.
0fe76f7379f2055b0856575b8cb0dbd897415b481a235e2e7f55f116f44f84d1user-coinbase.supportSaved 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
webmail.user-coinbase.support
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
利用不可→到達可能
https://radar.cloudflare.com/scan/a2497273-21f8-4c93-a379-810b73425b66
https://radar.cloudflare.com/scan/130a8294-4226-4f71-af6d-26abeebe67c8
到達可能→利用不可
到達可能→利用不可
11/91 engine detections
View sourceNo threat flag
View sourcePage captured
View sourcewebmail.user-coinbase.support
View source保存された類似ドメイン:255 件
255 件中 100 件を表示
コミュニティの 1 人が報告・初回確認 2025年11月30日
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 ↗
webmail.user-coinbase.support)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.