VirusTotal
3 / 89 engine detections
レポートを開く“Demo Protocol – Demo Protocol”
ブロックリスト掲載ドメイン: redirectsolutionprotocol.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 3/89 (alphaMountain.ai, Forcepoint ThreatSeeker, VIPRE); 1…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 89 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
redirectsolutionprotocol.pages.dev is an impersonation phishing page hosted on a free Cloudflare Pages subdomain and aimed at crypto users who expect to interact with a DeFi-style protocol. PhishDestroy first flagged it on 2026-09-07. The site went offline on 2026-09-16, and as of 2026-10-19 it remains dead with its content blocked by the hosting provider.
The page carried the title "Demo Protocol – Demo Protocol", a placeholder-style name rather than a recognisable brand, even though we classified the site as impersonation. Pages like this copy the look of a legitimate project's interface and push visitors to connect a wallet, "claim" something or fix a supposed issue. The name fragment "redirect solution" fits the usual pretext of a support or migration page. Once a visitor connects and signs, the operator can obtain token approvals or credentials and move funds out of the wallet.
Independent detection is modest. On 2026-09-17, 3 of 89 VirusTotal engines (alphaMountain.ai, Forcepoint ThreatSeeker and VIPRE) flagged the site, so most scanners would have let it through. ScamSniffer, a blocklist focused on Web3 fraud, lists it alongside PhishDestroy. That second listing is the stronger signal that the site targeted crypto wallets.
The subdomain was created on 2026-09-06, and PhishDestroy caught it a day later. That points to a disposable page set up for a short campaign. It was served through Cloudflare's network with a Canadian location, and its certificate came from Google Trust Services, issued automatically to every Cloudflare Pages site. The padlock therefore said nothing about whether the site was legitimate. The page lasted about ten days before the provider blocked it.
If you connected a wallet to this page and approved or signed anything, review your token approvals with a revocation tool, cancel any you don't recognise, and move remaining assets to a fresh wallet if you signed a permit or blind message. If you typed a seed phrase or private key, treat that wallet as compromised and empty it immediately. If you entered a password, change it and enable 2FA. Defenders should block the full subdomain and watch for other pages.dev hosts reusing the "Demo Protocol" title or similar redirect- and protocol-themed names.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
0692967d4c7d6cdb1d022ff4945930c103a4c33656bedb39988e0c07f232807cSaved 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
redirectsolutionprotocol.pages.dev
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
2→3
到達可能→利用不可
到達可能
No threat flag
View source3/89 engine detections
View sourceredirectsolutionprotocol.pages.dev
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 ↗
redirectsolutionprotocol.pages.dev)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.