VirusTotal
4 / 92 engine detections
レポートを開く“404 Not Found”
Googleなりすまし: julystake.com — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 92 engine detections
レポートを開く3 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
julystake.com is classified by PhishDestroy as an impersonation phishing page. Its name targets crypto holders looking for staking rewards. PhishDestroy first flagged it on 2026-09-27. As of 2026-10-19 the domain was still alive and redirecting visitors elsewhere rather than serving its own page. The page title shows "404 Not Found", while our classification is impersonation phishing.
Impersonation sites copy the look and wording of a trusted crypto service so visitors believe they are on the real platform. A staking-themed lure typically promises yield on deposited tokens. The visitor is then pushed to log in, enter a seed phrase, send funds, or connect a wallet and sign transactions. Whatever is handed over goes straight to the operators: account access, recovery phrases, or the tokens themselves. Because this domain currently redirects, the destination page can change without the domain changing.
Independent detection is still thin. On 2026-10-10, 4 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. It appears in 3 AlienVault OTX threat pulses, so other researchers have linked it to malicious activity. PhishDestroy is the only blocklist carrying it. Most browsers and security tools will not warn a visitor yet, so do not treat a missing warning as a sign the site is safe.
The domain was registered on 2026-07-18 through Fewmoretaps OU d/b/a Trustname.com, about ten weeks before it was detected. That gap is consistent with a domain held in reserve before being put to use. It sits behind Cloudflare, Inc. on an address geolocated to Canada, which hides the true origin server. Its certificate from Google Trust Services is a standard automated issue and says nothing about legitimacy.
If you entered a seed phrase or private key on julystake.com, treat that wallet as compromised. Create a new wallet and move any remaining assets immediately. If you connected a wallet and signed anything, review and revoke token approvals using a trusted approval checker. If you used a password there, change it wherever it is reused and turn on app-based 2FA. Do not send further "activation" or "unlock" payments to recover a staked balance. Defenders should block the domain at DNS and proxy level and report it to Cloudflare and the registrar.
Edge-IP の評判はこのドメインに起因しません。
lilith.ns.cloudflare.comLocation describes the IP network.
ed3c9d64378d679dd2c3089e0892516c124991cd3cb06d950af424e642669b08Saved 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.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://julystake.com/; server=cloudflare
julystake.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
1→2
3→1
2→3
3→2
2→3
No threat flag
View source4/92 engine detections
View source3 community references
View sourcejulystake.com
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 ↗
julystake.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.