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
rufuss.cn — No verificado. Suplantación de marca: MetaMask; Tipo de estafa: Impersonation. Resumen de las pruebas: VirusTotal 6/89 (alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 90/100. Registrador: 厦门易名科技股份有限公司.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
Stored evidence for rufuss.cn: VirusTotal recorded 4 detections among 91 scanners on 2026-08-28. 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 rufuss.cn. 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-28. 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-28 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 rufuss.cn in the snapshot dated 2026-08-28. 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 rufuss.cn 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 rufuss.cn on 2026-08-28. The MetaMask and SEAL blocklist snapshot is dated 2026-08-28 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-05-23. A URLScan reference was stored on 2026-08-28 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 rufuss.cn, the registrar field records 厦门易名科技股份有限公司; this is kept as an exact source value. The source stores 45.207.216.32 as the observed address in this record. The registration date for rufuss.cn is recorded as 2026-05-23. The stored ASN observation records 401701 and cognetcloud INC in this record. 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 rufuss.cn record states that VirusTotal recorded 4 detections among 91 scanners on 2026-08-28. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-28. PhishDestroy remains a separate publisher catalogue entry in the stored record. For rufuss.cn, the registrar field records 厦门易名科技股份有限公司; this remains separate from the other source fields. The observed address field in this record contains 45.207.216.32. The supported conclusion is bounded to the exact stored observations for rufuss.cn. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to rufuss.cn during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain rufuss.cn 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 rufuss.cn. The stored record does not justify extending that rule to 45.207.216.32 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:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='rufuss.cn', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<SOC
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.
Certificate hostname mismatch·
Emitido por Let's Encrypt· stored validity ends in 52 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
45.207.216.32
Network ASN
AS401701
Organization
Vapeline Technology
Observed location
Hong Kong, HK
Server header
nginx
Servidores de nombres 2
ns1.ename.net
ns2.ename.net
Location describes the IP network.
Certificado TLS
Issuer
Let's Encrypt
Valid from
2026-07-21 19:39:51
Valid until
2026-10-19 19:39:50
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-08-28 16:02:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8b2694f34df0dd4bd7e75a46ca41abf407f7376e0a36d4d858c18bc6dd4a076fCertificate names · 1 SANs
www.rufuss.cn
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationDesconocidoProbe Inconclusive20%2026-10-11 02:11:47 UTC
RDAP registrationDesconocido
Observed timelinelast reachable: 2026-10-07 22:37:01 UTClast content: 2026-10-07 22:37:01 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.
Tecnologías · 2 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 rufuss.cn· checked Aug 28, 2026
88
Needs Work
Performance
FCP
1.5s
First Contentful Paint
LCP
1.5s
Largest Contentful Paint
CLS
0.126
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
7.19s
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.
Threat First Observed2026-08-28 13:41:26 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 45.207.216.32.
Proceso de respuesta ante amenazas Pipeline
Descubrimiento
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Amenaza detectada
rufuss.cn 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.
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.
4 evidence signal groups linked0 reports recordedNo verificado
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 · rufuss.cn
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.
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.
