VirusTotal
15 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: 4913.bluefin.pr.app.bluefin.foundation — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 15/89 (ChainPatrol, alphaMountain.ai, BitDefender, CRDF…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 89 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
4913.bluefin.pr.app.bluefin.foundation is a phishing page that impersonates Cloudflare. It sits deep inside a multi-level subdomain chain that reuses the word "bluefin" twice. PhishDestroy first saw it on 2026-08-13, and its listing on MetaMask and SEAL blocklists shows that crypto users were the audience. The site has been offline since 2026-09-13, and on our last check on 2026-10-19 it was still dead with its content blocked by the provider.
Cloudflare impersonation pages copy the familiar security-check screens people see before reaching a website. That makes a fake "verify you are human" step or a login prompt look like routine friction. The victim is steered into typing credentials, approving an action or pasting something they were told to run, and the attacker keeps whatever access that grants. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial, while our classification is impersonation of the Cloudflare brand.
15 of 89 VirusTotal engines flag the domain as of 2026-09-14. The vendors include ChainPatrol, alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. The mix of crypto-focused services and mainstream antivirus engines matters because these groups detect independently of each other. MetaMask, SEAL and PhishDestroy all list the domain, so wallet software that consumes these feeds will warn users before the page loads.
The domain was registered through NameCheap, Inc. and resolved to 104.21.77.229 on Cloudflare, Inc.'s network, geolocated to Canada. Because the page was served through Cloudflare itself, the provider could step in directly. That is why visitors now get Cloudflare's phishing warning instead of the original content. The TLS certificate came from Google Trust Services (WE1), which is a standard automated issuance and does not indicate legitimacy.
If you entered a password or email on this page, change that password and turn on two-factor authentication anywhere you reuse it. If the page asked for a seed phrase or private key, treat that wallet as compromised and move your funds to a new wallet created on a clean device. If you followed any instructions to paste or run commands during a fake verification step, scan the device and rotate your saved credentials. Defenders should block the whole bluefin.foundation parent domain and its subdomains, and should search proxy logs for visits since 2026-08-13.
Last checked
For the registrable domain bluefin.foundation 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 の評判はこのドメインに起因しません。
trace.ns.cloudflare.comLocation describes the IP network.
0516ad7161c4e2361c71a4931f0b9ce0c437204614c701d3c2baaf9a6b2bd197bluefin.foundationSaved 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 4913.bluefin.pr.app.bluefin.foundation · checked Sep 14, 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.
4913.bluefin.pr.app.bluefin.foundation
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
利用不可→到達可能
10→15
到達可能→利用不可
No threat flag
View source15/89 engine detections
View source4913.bluefin.pr.app.bluefin.foundation
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
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 ↗
4913.bluefin.pr.app.bluefin.foundation)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.