tgeljvnb.shop
“400 No required SSL certificate was sent”
tgeljvnb.shop — Contenuto non disponibile. Simulazione del marchio: Unknown; Tipo di truffa: Impersonation. Riepilogo delle prove: VirusTotal 14/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); Spamhaus DBL_SPAM; CF Radar malicious; PhishDestroy score 92/100. Registrar: TLD Registry (.shop).
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
Riepilogo delle prove
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 22: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.
Informazioni sulla sicurezza di rete
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.
Pipeline di risposta alle minacce
Stato della lista di blocco pubblica
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
Acquisizione salvata · 2 sources
Analisi dei domini
Dettagli tecniciDNS, SAN SSL, timestamp
ICANN OVERSIGHT
Accreditamento e contesto RAA
Accreditamento e contesto 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.
Analisi di VirusTotal
Dati e relazioni esterne
PD-1788736214-tgeljvnb.shop Recipient: abuse@gmo.jp Questo sito ti ha influenzato in qualche modo?
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Segnalalo alle autorità locali
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.
Verifica qualsiasi dominio
Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica
Scansiona oraSegnala un tentativo di phishing
Segnala i domini sospetti al nostro database delle minacce — proteggi la comunità
SegnalaFeed in tempo reale sulle minacce
Segnalazioni recenti di phishing e modifiche osservate della disponibilità
MonitoraRimani informato, rimani al sicuro
Controlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo