Seguridad de dominio e inteligencia sobre amenazas
slon11.su
“KRAKEN — Вход в аккаунт”
Registrador
REGRU-SU
Resolved IP
31.31.198.2
Registered
28/08/2026
Veredicto de amenaza
Crítico100/100
Disponibilidad
Contenido no disponibleEl contenido no estaba disponible en la última observación.
Señales de riesgo
VirusTotal detecciones: 6/91Spamhaus DBL: DBL_PHISHCoincidencias de la lista de bloqueo almacenadas: 2URLQuery threat systems: 1 alertSuplantación de marca: Kraken
Motores de seguridad que informan una detección: 6. Listas de bloqueo públicas que informan una coincidencia: 2. Tenga extrema precaución: no ingrese credenciales o información personal.
Resumen del informe
slon11.su — Contenido no disponible. Suplantación de marca: Kraken; Tipo de estafa: Impersonation. Resumen de las pruebas: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); URLQuery 1 alert; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Registrador: REGRU-SU.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
Stored evidence for slon11.su: VirusTotal recorded 4 detections among 91 scanners on 2026-08-31. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for slon11.su. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 4 detections among 91 scanners in the stored snapshot dated 2026-08-31. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-31 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for slon11.su in the snapshot dated 2026-08-31. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains slon11.su as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed slon11.su on 2026-08-31. The MetaMask and SEAL blocklist snapshot is dated 2026-08-31 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-08-28. A URLScan reference was stored on 2026-08-31 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For slon11.su, the registrar field records REGRU-SU; this is kept as an exact source value. The source stores 31.31.198.2 as the observed address in this record. The registration date for slon11.su is recorded as 2026-08-28. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The slon11.su record states that VirusTotal recorded 4 detections among 91 scanners on 2026-08-31. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-31. PhishDestroy remains a separate publisher catalogue entry in the stored record. For slon11.su, the registrar field records REGRU-SU; this remains separate from the other source fields. The observed address field in this record contains 31.31.198.2. The supported conclusion is bounded to the exact stored observations for slon11.su. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to slon11.su during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain slon11.su as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to slon11.su. The stored record does not justify extending that rule to 31.31.198.2 or to other infrastructure records.
Análisis de detección y evasión
Comprobación del enmascaramiento y la distribución del tráfico
Aún no se ha escaneadoAún no se ha registrado ninguna diferencia entre los rastreadores y los navegadores
Observaciones almacenadas de rastreadores frente a navegadores para este servidor, además de una comprobación en tiempo real de la huella digital para sistemas de distribución de tráfico al estilo Keitaro.
Indicador de camuflaje almacenado
Aún no se ha escaneado
Último escaneo de camuflaje
Nota del escáner:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='slon11.su', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOCK
Comprobación de huellas dactilares en directo en TDS
Siete huellas de Keitaro, además de una comparación entre el rastreador y el navegador, que se ejecutan desde el escáner PhishDestroy cuando este panel está abierto.
Qué contabilizamos
Tiempo transcurrido desde el primer informe de abuso almacenado hasta la primera observación de que el contenido no estaba disponible. Esto no establece la causa.
Qué contiene cada informe
Los registros de informes salientes almacenados pueden hacer referencia a evidencia disponible en ese momento, como veredictos de proveedores, datos de registro, detalles de alojamiento, clasificaciones o capturas de pantalla. Esta página no infiere la carga útil entregada, el recibo, el acuse de recibo o la acción exacta por parte de un destinatario.
Detalles técnicosProvenance & timestamps
Primera detección31/08/2026
Submitted URLhttp://slon11.su/
Favicon Hash
ID del caso
Título de la página
KRAKEN — Вход в аккаунт
Impersonates
Kraken
Certificado TLS
Certificate hostname mismatch·
Emitido por GlobalSign nv-sa· stored validity ends in 196 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
31.31.198.2
Network ASN
AS197695
Organization
Reg.Ru
Observed location
Moscow, RU
Server header
nginx
Servidores de nombres 2
ns1.hosting.reg.ru
ns2.hosting.reg.ru
Mail routing 2 MX records
mx1.hosting.reg.rupriority 10
mx2.hosting.reg.rupriority 20
Location describes the IP network.
Certificado TLS
Issuer
GlobalSign nv-sa
Valid from
2026-08-28 14:53:18
Valid until
2027-03-15 14:53:18
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-08-31 10:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint75b63335ab6e15f6415ac3d184395b22420fc2170f517e466c102a50a6046267Certificate names · 4 SANs
autodiscover.slon11.su
mail.slon11.su
owa.slon11.su
www.slon11.su
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivoreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationDesconocidoProbe Inconclusive20%2026-10-11 01:14:18 UTC
RDAP registrationDesconocido
Observed timelinelast reachable: 2026-09-08 22:16:44 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-08 22:16:44 UTC → 2026-09-30 16:14:55 UTC · 521.97hmidpoint estimate ≈ 2026-09-19 19:15:49 UTC · precision low · basis bounded
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.
Tecnologías · 1 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Google PageSpeed Insights — mobile performance audit of slon11.su· checked Aug 31, 2026
100
Good
Performance
FCP
0.81s
First Contentful Paint
LCP
0.81s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.89s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-10 22:04:57 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-08-31 07:52:09 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 31.31.198.2.
Proceso de respuesta ante amenazas Pipeline
Descubrimiento
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Amenaza detectada
slon11.su detectados y puestos en cola para su análisis completo
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Las últimas comprobaciones almacenadas indican que el contenido informado no está disponible; esto no establece quién o qué causó el cambio.
11/09/2026
Tiempo hasta la primera indisponibilidad
254 horas transcurrieron desde la detección hasta la primera observación no disponible.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
PDF notice generated Notice text archived (650 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 (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
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.
6 evidence signal groups linked1 reports recordedContenido no disponible
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.
¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales.Más información sobre el fraude en las ayudas de recuperación →
Template-based draft · optional AI wording assistance requires separate consent
Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
Infraestructura e informes relacionados
Las relaciones almacenadas se agrupan por el atributo de coincidencia exacta. Un proveedor o registrador compartido por sí solo no prueba la propiedad común.
Enlace directo Comparte un registro o un kit de phishing idéntico.
Señal de apoyo Comparte infraestructura o una marca de destino; no es prueba de que se trate de un único operador.
Solo para consulta Incluido en la lista de navegación; no comparte ningún atributo con este host.
Mapa de infraestructuras · slon11.su
Cada línea representa un motivo por el que un dominio está vinculado a este servidor. El tamaño de los nodos indica las detecciones de VirusTotal y los nodos con línea discontinua ya están fuera de línea. A continuación se incluyen las listas completas.
El contenido coincide4
El mismo hash del favicon o el mismo título de página que este servidor.
Registrados a través del mismo proveedor de registro. Un proveedor de registro presta servicio a millones de clientes que no tienen relación entre sí, por lo que este dato solo agrupa los registros, en lugar de demostrar que exista un vínculo.
Informes agregados recientemente de la base de datos PhishDestroy. Estos enlaces de descubrimiento no implican infraestructura ni propiedad compartida.
Denunciar 
