VirusTotal
0 / 89 engine detections
レポートを開く“Vote 0x03...9E1b — pons”
ブロックリスト掲載ドメイン: pons-voting-g0.netlify.app — コンテンツが利用できません (HTTP 404). 証拠の概要: VirusTotal 0/89; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
0 / 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
pons-voting-g0.netlify.app was an impersonation phishing page dressed up as a governance vote for pons. Its title, "Vote 0x03...9E1b — pons", mimicked a proposal or ballot page, which targets token holders and community members who expect to vote with their wallets. PhishDestroy first saw it on 2026-09-15. It went offline on 2026-09-16, and as of 2026-10-19 the address is dead with nothing served at the root.
Fake voting pages rely on urgency and legitimacy. A holder sees what looks like an official ballot, with a shortened address-style identifier in the title like a real proposal, and is asked to connect a wallet to cast a vote. The vote button then triggers a wallet prompt. That prompt can be a token approval, a permit signature or a transaction rather than a harmless vote, and once confirmed it lets the operator move the victim's assets. Because governance votes often do require a signature, victims have little reason to question the request.
MetaMask and SEAL both list the domain alongside PhishDestroy. That gives two independent wallet-security sources backing the impersonation classification. VirusTotal tells a different story, with 0 of 89 engines flagging it on 2026-09-17. That scan came a day after the page had already gone dark, so a clean result here says more about how short-lived the page was than about whether it was safe.
The page sat on a free Netlify subdomain, so there was no domain to register and it could be launched and discarded within hours. The window between first sighting and going offline was about one day, a typical disposable-campaign pattern. Traffic resolved to Amazon infrastructure in Germany, which is Netlify's ordinary delivery network. The DigiCert certificate is Netlify's standard one, so the padlock showed only that the connection was encrypted and nothing about who ran the page.
If you connected a wallet to this page, review its token approvals and permissions in a revocation tool and cancel anything you do not recognise, especially approvals granted around 2026-09-15. If you signed a transaction or permit, move the remaining funds to a fresh wallet whose seed phrase has never touched that browser. Treat every vote link from a direct message or social reply as suspect, and reach pons governance only through its official, bookmarked channels. Defenders should block the hostname and watch for sibling Netlify subdomains using the same pons voting lure.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x0339f5459FC690aC85F1782e15782A151b4A9E1bFormat validated · Domain analysisIoC extraction recorded 2026-09-16 04:00:22 UTC
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
Saved 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 pons-voting-g0.netlify.app · checked Sep 15, 2026
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
pons-voting-g0.netlify.app
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
到達可能→利用不可
No threat flag
View source0/89 engine detections
View sourcepons-voting-g0.netlify.app
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 ↗
pons-voting-g0.netlify.app)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.