tgeljvnb.shop
“400 No required SSL certificate was sent”
tgeljvnb.shop — Contenu indisponible. Usurpation de l'identité de la marque : Unknown; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 14/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); Spamhaus DBL_SPAM; CF Radar malicious; PhishDestroy score 92/100. Bureau d’enregistrement: TLD Registry (.shop).
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
Résumé des preuves
PhishDestroy first observed tgeljvnb.shop on Sep 6, 2026. Stored content metadata identifies Unknown as the apparent target. The captured page title is “400 No required SSL certificate was sent”. Stored page analysis classifies the content as impersonation. Campaign clustering links the hostname to the Unknown kit. Current evidence score: 92/100 (critical).
Positive findings are stored from 3 sources: VirusTotal, Spamhaus DBL, and Cloudflare Radar. VirusTotal recorded 14 detections among 89 engines: alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Fortinet, G-Data, Gridinsoft, LevelBlue, Lionic, SOCRadar, Sophos, VIPRE on Sep 8, 2026 at 18:20 UTC. Spamhaus DBL: DBL_SPAM on Sep 7, 2026 at 02:30 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the dga domains category; its verdict timestamp was not retained. Non-positive and contextual checks: AlienVault OTX listed 4 community pulse references (not vendor detections) on Sep 8, 2026 at 18:22 UTC. The separate external-blocklist snapshot contained no matches on Sep 20, 2026 at 18:20 UTC. Google Safe Browsing returned no flag on Sep 8, 2026 at 18:21 UTC. URLScan completed without a malicious verdict (score 0) on Sep 7, 2026 at 17:08 UTC.
No conclusive timestamped HTTP response is stored. Registration records for the domain list TLD Registry (.shop) as the registrar and Jun 15, 2026 as the creation date. At collection time, the hostname resolved to 27.124.47.186 on AS152194 (CTG Server Limited). The recorded endpoint location is Sheung Wan, HK. The stored server header is nginx/1.18.0 (Ubuntu). DOM analysis on Sep 7, 2026 at 02:22 UTC returned 83/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Telegram as the certificate issuer with validity through Sep 14, 2028; checked Sep 7, 2026 at 07:02 UTC.
The content indicators and 3 positive source findings support the current Unknown-themed impersonation classification.
Renseignements sur la sécurité réseau
Forensic History & Detection Timeline
-
Domain Status Transition Sep 11, 2026 · 00:49 UTCDomain state transitioned from alive to dead.
-
Threat First Observed Sep 7, 2026 · 01:13 UTCDomain ingestion complete. Initial state is marked as unknown.
Processus de réponse aux menaces Pipeline
Statut de la liste de blocage publique
Evasion analysis
Cloaking & traffic-distribution check
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
Scanner note: dns_error: raw=dns_error; via=local_dns_prefilter
Capture enregistrée · 2 sources
Informations sur les domaines
Détails techniquesDNS, SAN SSL, horodatages
ICANN OVERSIGHT
Contexte de l’accréditation et du RAA
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.
Analyse VirusTotal
Données factuelles et rapports externes
PD-1788736214-tgeljvnb.shop Recipient: abuse@gmo.jp Ce site vous a-t-il affecté ?
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.
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 →.
Vérifier n'importe quel domaine
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignaler une tentative d'hameçonnage
Signalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerFlux d'alertes en temps réel
Rapports de phishing récents et changements de disponibilité observés
SurveillerRestez 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