yenilenmis.blog
“yenilenmis.blog”
yenilenmis.blog — Dernier actif connu (HTTP 200). Usurpation de l'identité de la marque : Unknown; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 17/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLQuery 2 det.; URLScan capture; CF Radar malicious; PhishDestroy score 100/100. Bureau d’enregistrement: Realtime.
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 yenilenmis.blog on Sep 20, 2026. Stored content metadata identifies Unknown as the apparent target. The captured page title is “yenilenmis.blog”. Stored page analysis classifies the content as impersonation. Current evidence score: 100/100 (critical).
Positive findings are stored from 3 sources: VirusTotal, Cloudflare Radar, and URLQuery. VirusTotal recorded 17 detections among 89 engines: alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot on Sep 20, 2026 at 23:39 UTC. Cloudflare Radar classified the hostname as malicious and assigned the categories malware and security threats; its verdict timestamp was not retained. URLQuery recorded 2 detections; no observation timestamp was retained. Non-positive and contextual checks: On Sep 20, 2026 at 23:39 UTC, AlienVault OTX listed 4 community pulse references (not vendor detections); Google Safe Browsing returned no flag. The separate external-blocklist snapshot contained no matches on Sep 20, 2026 at 22:20 UTC. URLScan captured the page on Sep 20, 2026 at 21:50 UTC.
HTTP 200 was recorded on Sep 20, 2026 at 23:04 UTC. Registration records for the domain list Realtime Register B.V. as the registrar and Mar 24, 2023 as the creation date. At collection time, the hostname resolved to 138.197.50.19 on AS14061 (DigitalOcean, LLC). The recorded endpoint location is Clifton, US. The stored server header is Apache/2.4.58 (Ubuntu). DOM analysis on Sep 20, 2026 at 22:20 UTC returned 98/100. The evidence archive retains 3 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / YE1 as the certificate issuer with validity through Oct 28, 2026; checked Sep 20, 2026 at 22: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 21, 2026 · 01:04 UTCDomain state transitioned from alive to dead.
-
Threat First Observed Sep 20, 2026 · 23:33 UTCDomain ingestion complete. Initial state is marked as unknown pointing to IP
138.197.50.19.
Processus de réponse aux menaces Pipeline
Statut de la liste de blocage publique
Evasion analysis
Cloaking suspected: scanner and victim titles differ
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
- Server header seen by scanner
Apache/2.4.58 (Ubuntu)
Scanner note: parked: raw=parked; http=200; via=https_direct; server=Apache/2.4.58 (Ubuntu)
Capture enregistrée · 3 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
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