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
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.