Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
julystake.com favicon

julystake.com

“404 Not Found”

Bureau d’enregistrement
Fewmoretaps OU d/b/a T…
Resolved IP
188.114.97.1
Registered
18/07/2026
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 4/92 Libellé de marque automatique : Google
OTX: 3 refs 27/09/2026 CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 4. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Résumé du rapport

Usurpation de Google: julystake.com — Dernier actif connu (HTTP 301). Résumé des preuves: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 4 / 92 · OTX 3 references 5 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Renseignements sur la sécurité réseau Registrar context
Registrar context Trustname
Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
Trustname Investigation

Analysis

Critique
VirusTotal
4 / 92
OTX
3 community refs
Page captures
2

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 2 captures

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainesdrainerfraudmonthlyphishdestroyphishingscam
Bureau d’enregistrement Fewmoretaps OU d/b/a T… BY(BY) PhishDestroy Investigation
Contact anti-abus["abuse@trustname.com"]
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 18/07/2026 (94d) — Expires 18/07/2027
Statut HTTP301 Moved Permanently
Détails techniquesProvenance & timestamps
Première détection27/09/2026
DOM Analysisanalyzed 09/10/2026score 81/100
Submitted URLhttps://julystake.com/
Favicon Hash
Observed page title
404 Not Found
Certificat TLS
Émis par Google Trust Services / WE1 · stored validity ends in 54 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.1
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 1

  • lilith.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Google Trust Services / WE1
Valid from
2026-09-15 02:45:14
Valid until
2026-12-14 03:45:11
Validity
Within stored validity dates
Collection time
2026-10-11 07:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprinted3c9d64378d679dd2c3089e0892516c124991cd3cb06d950af424e642669b08

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 10:07:10 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-20 10:07:10 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-20 10:07:10 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Casino / Gambling License Verification
Unverified gambling license
This domain markets casino/gambling services. Scam casinos routinely display fake Curaçao, MGA, or Kahnawake license badges that don’t exist in the real registries. Always verify the license number against the official regulator database before depositing. If the site shows a seal but no clickable registry link — or the linked registry page doesn’t exist — treat it as fraudulent.
Curaçao eGaming (official) Malta Gaming Authority UK Gambling Commission PA Gaming Control Kahnawake Gaming Gibraltar Gambling
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

4 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

redirect: raw=redirect_301; http=301; via=http_proxy; location=https://julystake.com/; server=cloudflare

Browser
404 Not Found
Crawler
301 Moved Permanently
julystake.com
Résultat enregistré
Cloaked / Filtered
Stored observation history23

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Earlier observations 18
  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  13. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  14. VirusTotal · Detection count

    1→2

  15. VirusTotal · Detection count

    3→1

  16. VirusTotal · Detection count

    2→3

  17. VirusTotal · Detection count

    3→2

  18. VirusTotal · Detection count

    2→3

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    4/92 engine detections

    View source
  3. AlienVault OTX

    3 community references

    View source
  4. Added to PhishDestroy

    julystake.com

    View source

Données factuelles et rapports externes

Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

4 evidence signal groups linked 0 stored notification records Dernier actif connu

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

Template-based draft · optional AI wording assistance requires separate consent

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Que dois-je faire tout de suite ?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment julystake.com)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/julystake.com"
  title="PhishDestroy threat report for julystake.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>