Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@vercel.com.
The latest stored availability evidence still shows the domain reachable; 6 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
lm[.]fm
Análisis de phishing y seguridad de lm.fm
“Limey - Simple, free, fully responsive sites”
lm.fm — Encubierto · accesible (HTTP 308). Resumen de las pruebas: VirusTotal 0/91; URLQuery 4 alerts; Spamhaus DBL_PHISH; cloaking observed; PhishDestroy score 83/100. Registrador: NameCheap.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
PhishDestroy first observed lm.fm on Feb 5, 2026. The captured page title is “Limey - Simple, free, fully responsive sites”. Current evidence score: 83/100 (critical).
Positive findings are stored from 3 sources: Spamhaus DBL, DNS security resolvers, and URLQuery. Spamhaus DBL: DBL_PHISH on Jul 14, 2026 at 10:35 UTC. DNS security checks returned 6 blocking results across 14 tested policies: Adguard Default, Adguard Family, Control D Adblock, Control D Family, Control D Malware, Quad9 Secure; no observation timestamp was retained. URLQuery recorded 4 threat-system alerts on Feb 5, 2026 at 13:25 UTC. Non-positive and contextual checks: VirusTotal recorded 0 detections among 91 engines on Aug 8, 2026 at 02:09 UTC. AlienVault OTX listed 1 community pulse reference (not vendor detections) on Mar 1, 2026 at 10:11 UTC. The separate external-blocklist snapshot contained no matches on Aug 8, 2026 at 10:20 UTC. Google Safe Browsing returned no flag on Mar 2, 2026 at 20:32 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 02:54 UTC. The 0/91 VirusTotal snapshot and the positive findings above are conflicting observations from different sources or collection times.
Cloaking was recorded with HTTP 308 on Aug 8, 2026 at 10:31 UTC. The cloaking probe recorded content split conditional delivery at 1/100 on Aug 8, 2026 at 10:31 UTC: redirect: raw=redirect_308; http=308; via=https_proxy; location=https://limey.io/; server=Vercel. Registration records for the domain list NameCheap, Inc. as the registrar. At collection time, the hostname resolved to 66.33.60.129 on AS16509 (Amazon.com, Inc.). The IP and ASN identify shared Vercel edge infrastructure; the origin server is not established by this address. DOM analysis on Jul 9, 2026 at 02:21 UTC returned 83/100. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and URLQuery. TLS metadata lists R13 as the certificate issuer with validity through May 26, 2026; checked Mar 15, 2026 at 05:40 UTC.
The content indicators and 3 positive source findings support the current phishing classification. The stored fields do not identify an impersonated brand or victim interaction.
Inteligencia de seguridad de red
Proceso de respuesta ante amenazas Pipeline
Estado de la lista de bloqueados pública
Tecnologías · 8 identified
Cloud computing platform offering compute, storage, and networking services.
Cloud platform for frontend deployment, optimized for Next.js.
Customer support ticketing platform.
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Análisis de VirusTotal
Evidencias archivadas
Análisis del rendimiento del sitio
Google PageSpeed Insights — mobile performance audit of lm.fm · checked Mar 2, 2026
Datos y informes externos
PD-20260205-221F5E Recipient: abuse@vercel.com ¿Te ha afectado esta página web?
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.
Informa a las autoridades locales
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
Comprobar cualquier dominio
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraDenunciar un intento de phishing
Envía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarFlujo de amenazas en tiempo real
Informes de phishing recientes y cambios de disponibilidad observados
MonitorizarMantente informado, mantente a salvo
Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.