VirusTotal
4 / 89 engine detections
レポートを開く“403 Forbidden”
Each check shows its own collection time. Zero detections do not guarantee safety.
Googleなりすまし: rbbs.ecotrustfbnn.com — コンテンツが利用できません. 証拠の概要: VirusTotal 4/89 (CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); PhishDestroy score 71/100.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 89 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開く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
rbbs.ecotrustfbnn.com is an impersonation phishing page on a throwaway subdomain built to pass as a legitimate, trustworthy service. It targets people who reach it through links in messages, ads or social posts and believe they are dealing with the real provider. PhishDestroy first flagged it on 2026-09-05. The site has been offline since 2026-10-14 and was still unreachable when last checked on 2026-10-19.
Impersonation pages copy the look, wording and flow of a known brand so the visitor relaxes and follows instructions. The usual goal is to collect account credentials, personal details or a payment, and in the crypto space a wallet recovery phrase, which gives the operator direct control of whatever the victim enters. When last served, the page returned the title "403 Forbidden", while our classification places it as an impersonation phishing page.
On 2026-09-18, VirusTotal showed 4 of 89 engines flagging the domain: CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a small share, so most security tools would have let it load without warning. The four flags come from independent threat-intelligence and web-filtering vendors, and they match PhishDestroy's own listing, which is the only blocklist carrying it.
The parent domain was registered through NameSilo, LLC on 2026-01-17, almost eight months before PhishDestroy detected the subdomain. That gap points to a domain set up ahead of time and kept quiet until it was used. The site ran on FranTech Solutions in the United States behind a free Let's Encrypt certificate, so the browser padlock showed only that the connection was encrypted. It says nothing about who ran the site.
If you typed a password on this site, change it now on the genuine service and on any other account that uses the same password. Then turn on app-based two-factor authentication. If you entered card or bank details, contact your bank to block the card and dispute the charges. If you entered a wallet recovery phrase, treat that wallet as compromised and move your funds to a newly created wallet. Defenders should block the domain and its parent in DNS and web filters, and search mail and proxy logs from 2026-09-05 onward for any contact with it.
ns1.robotichosting.comns2.robotichosting.comLocation describes the IP network.
d1d087184cf69975741eddaf80d728d7c6984fb6c1e072f020fb426bbdc93c53ecotrustfbnn.comftp.ecotrustfbnn.commail.ecotrustfbnn.compop.ecotrustfbnn.comsmtp.ecotrustfbnn.comwww.ecotrustfbnn.comwww.rbbs.ecotrustfbnn.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.rbbs.ecotrustfbnn.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of rbbs.ecotrustfbnn.com · checked Sep 5, 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.
rbbs.ecotrustfbnn.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
2→3
1→2
到達可能
No threat flag
View source4/89 engine detections
View sourcerbbs.ecotrustfbnn.com
View sourcePage captured
View sourceListed 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 ↗
rbbs.ecotrustfbnn.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.