VirusTotal
1 / 89 engine detections
レポートを開く“Decentralized Launchpad”
ブロックリスト掲載ドメイン: sync-validate.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 1/89 (LevelBlue); PhishDestroy score 61/100. レジストラ: Cloudflare Pages.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
1 / 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
sync-validate.pages.dev is an impersonation phishing page that presented itself as a "Decentralized Launchpad", the kind of token-sale platform crypto investors use to buy into new projects early. Its targets are people chasing presales and airdrops who expect to connect a wallet to take part. The page title advertises a generic launchpad rather than a named brand, while our classification is impersonation phishing. PhishDestroy first flagged it on 2026-09-05. It has been offline since 2026-09-16, its content blocked by the hosting provider, and it was still down at the last check on 2026-10-19.
Fake launchpads borrow the look and language of real token-sale platforms so that a wallet prompt feels like a routine step toward an allocation. The subdomain's "sync" and "validate" wording echoes a common lure in which visitors are told their wallet must be synchronised or validated before they can participate. In schemes like this, the victim is pushed to sign a token approval or transaction that hands control of their assets to the attacker, or to type a recovery phrase into a form. Either way, the loss is the contents of the wallet, often drained within minutes and with no way to reverse it.
Independent detection was thin. On 2026-09-17 only one of 89 VirusTotal engines, LevelBlue, flagged the site, and the only blocklist carrying it is PhishDestroy's own. That low count reflects how quickly short-lived pages on free hosting can appear and disappear before most vendors catch them, so a clean scan from other tools would not have meant the page was safe.
The project was created on Cloudflare Pages on 2026-09-02, just three days before we detected it, and was taken offline after about two weeks. It sat on Cloudflare's network, with the serving address geolocated to Canada. The HTTPS certificate came from Google Trust Services, issued automatically as for any Pages site, so the padlock in the browser said nothing about whether the page was legitimate.
If you connected a wallet to this page, use a token-approval checker to revoke any permissions you granted during the visit, and move remaining funds to a fresh wallet if you are unsure what you signed. If you entered a recovery phrase, treat that wallet as fully compromised and transfer everything to a new wallet generated on a clean device right away. Join token sales only through links published on a project's verified channels. Defenders should block the domain and watch for lookalike pages.dev subdomains reusing "sync" or "validate" wording or the "Decentralized Launchpad" title.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
5feec07f91f1bec3b16e0f55492252da57ece43d3eaf7fce5b8f7a94939e04dcSaved 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 sync-validate.pages.dev · checked Sep 15, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
sync-validate.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
到達可能→利用不可
到達可能
No threat flag
View source1/89 engine detections
View sourcesync-validate.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 ↗
sync-validate.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.