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

hellcase.london

“Hellcase – CS2 Cases, Upgrades”

Bureau d’enregistrement
Hosting Concepts
Resolved IP
188.114.97.3
Registered
01/05/2026
PhishDestroy assessment Critique
Disponibilité Masqué · accessible Accessibilité observée grâce aux contrôles de masquage Observé · HTTP probe
Détections VirusTotal : 12/91 Correspondances de la liste de blocage stockée : 2 URLQuery threat systems: 1 alert Type d'arnaque : Impersonation Dernier actif connu
OTX: 16 refs 09/06/2026 1 Report Sent CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 12. Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@registrar.eu. The latest stored availability evidence still shows the domain reachable; 4 months has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
4 months
Reports sent
1
Latest case ID
PD-20260609-F4F5EF
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Résumé du rapport

Hameçonnage: hellcase.london — Masqué · accessible (HTTP 200). Résumé des preuves: VirusTotal 12/91 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint…

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

Source evidenceVirusTotal 12 / 91 · OTX 16 references 7 sources

Blocs DNS

14 vérifié — aucun blocage

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
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
Nextron YARA rules hellcase.london/templates/hellcase/js/index.js malware Unique code from Jetriz, Swid & Jeniva of the Tetris framework

Analysis

Critique
VirusTotal
12 / 91
OTX
16 community refs
Page captures
2

PhishDestroy threat report

This domain is currently flagged as a high‑risk generic phishing site. The site resolves to 188.114.97.3, which belongs to Cloudflare, Inc. in Canada and is protected by a Let’s Encrypt/E8 certificate. HTTP requests return status 200 and the service supports HTTP/3, indicating a modern web stack. Technology fingerprints include PHP behind Cloudflare. The public page title reads “Hellcase – CS2 Cases, Upgrades”. Infrastructure analysis shows the domain was registered through Hosting Concepts B.V. d/b/a Registrar.eu. Reputation data lists the domain on three security blocklists and it appears in two AlienVault OTX threat pulses. VirusTotal scans have recorded 15 detections out of 91 scanners, and the domain is specifically blocked by PhishDestroy, MetaMask, and SEAL. Gridinsoft assigns a trust score of 0 / 100. The combination of multiple vendor detections, blocklist listings, and low trust score supports a high confidence that the site is being used for phishing. However, the exact content and phishing payload have not been publicly disclosed, so the precise lure and target audience remain unknown. Defenders should consider adding the domain to deny‑list controls, monitor DNS queries for the IP address, and enforce TLS inspection to capture any credential submissions. Ongoing observation of related traffic and correlation with user reports is recommended to confirm exploitation attempts.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Répertorié View source
PhishDestroy PhishDestroy list View source
SEAL Répertorié View source

Last checked

Capture enregistrée · 2 captures

Observed page title
Hellcase – CS2 Cases, Upgrades
Automated brand references
Across Ankr Apple Base Chase Counter-strike Cs2 Csgo +3
Certificat TLS
Émis par Let's Encrypt · stored validity ends in 34 days

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-06activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement Hosting Concepts GB(GB)
Contact anti-abus["abuse@registrar.eu"]
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 01/05/2026 (172d) — Expires 01/05/2027
Cloaking Cloaking Detected Content divergence · score 2/6
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
server: cloudflare title: Hellcase – CS2 Cases, Upgrades & Daily Free Rewards
checked 20/10/2026
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection09/06/2026
DOM Analysisanalyzed 09/10/2026score 100/10011 brand signals
Submitted URLhttp://hellcase.london/
Favicon Hash
ID du dossier
ICANN OVERSIGHT

Contexte de l’accréditation et du RAA

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
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

  • woz.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt
Valid from
2026-08-27 14:55:23
Valid until
2026-11-25 14:55:22
Validity
Within stored validity dates
Collection time
2026-10-10 04:03:36 UTC
Collection source
PhishDestroy collector
Certificate fingerprint901a5d9ac19d705351375f781c2e268b430d0f00991c3ce91a2be4b80ec99545

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-19 22:30:33 UTC

Primary outcome Contenu actif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenu actif Ordinary HTTP content served 90% 2026-10-19 22:30:33 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:35:33 UTC last content: 2026-10-19 22:30:33 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

12 / Les fournisseurs de sécurité 91 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of hellcase.london · checked Jun 26, 2026

96
Good
Performance
FCP
1.06s
First Contentful Paint
LCP
2.26s
Largest Contentful Paint
CLS
0.015
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.28s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

Different responses detected

content_divergence · alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

Browser
Hellcase – CS2 Cases, Upgrades
Crawler
Hellcase – CS2 Cases, Upgrades & Daily Free Rewards
hellcase.london
Résultat enregistré
Keitaro TDS
Stored observation history18

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→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

Earlier observations 13
  1. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  6. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  7. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  8. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  9. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  10. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  11. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  12. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  13. VirusTotal · Detection count

    14→15

Recorded activity

5 entries
  1. AlienVault OTX

    16 community references

    View source
  2. VirusTotal

    12/91 engine detections

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. Abuse report sent

    PD-20260609-F4F5EF

    abuse@registrar.eu
  5. Added to PhishDestroy

    hellcase.london

    View source

Signalements communautaires

Signalé par 1 membre de la communauté ; première observation le 09/06/2026

Signalements enregistrés
1
URL signalées uniques
1
Accepté1

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260609-F4F5EF Recipient: abuse@registrar.eu
Page title stored with report: Hellcase – CS2 Cases, Upgrades & Daily Free Rewards
PDF notice generated Notice text archived (602 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (GB):
Computer Misuse Act 1990
Fraud Act 2006
Communications Act 2003 - Section 127
UK law criminalizes unauthorized computer access, fraud, and malicious communications.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

6 evidence signal groups linked 1 stored notification records Masqué · accessible
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 hellcase.london)
  • 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/hellcase.london"
  title="PhishDestroy threat report for hellcase.london"
  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>