Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
hoomepage-ledger.zapier.app favicon

hoomepage-ledger.zapier.app

“Forms”

Registrador
Name.com
Resolved IP
64.239.123.129
Registered
20/09/2022
PhishDestroy assessment Crítico
Disponibilidad Último activo conocido Última observación de accesibilidad almacenada Observado · HTTP probe
VirusTotal detecciones: 15/89 Etiqueta automática de marca: Ledger
06/09/2026 CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 15. Tenga extrema precaución: no ingrese credenciales o información personal.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Resumen del informe

Suplantación de Ledger: hoomepage-ledger.zapier.app — Último activo conocido (HTTP 308). Resumen de las pruebas: VirusTotal 15/89 (Criminal IP…

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Source evidenceVirusTotal 15 / 89 5 sources

VirusTotal

15 / 89 engine detections

Abrir informe

Google Safe Browsing

No threat flag

Abrir informe

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Crítico
VirusTotal
15 / 89
Page captures
2

PhishDestroy threat report

Overview

hoomepage-ledger.zapier.app is a phishing page that impersonates Ledger, the hardware wallet maker, and targets people who keep crypto on Ledger devices. The misspelled "hoomepage" label is meant to pass at a glance as an official Ledger homepage. PhishDestroy first detected it on 2026-09-06. It was still alive when last checked on 2026-10-19.

How the scam works

The page carries the generic title "Forms" rather than any Ledger branding, but we classify it as Ledger impersonation phishing. Schemes like this typically tell the visitor that their device needs a sync, update or security check. They then ask the visitor to type the 24-word recovery phrase into a form. Anyone holding that phrase can rebuild the wallet on their own device and move every asset out, and the hardware wallet cannot block it. Ledger never asks for a recovery phrase through a website or form.

Evidence

When VirusTotal checked the domain on 2026-09-17, 15 of 89 security engines flagged it. They include ESET, BitDefender, Fortinet, CRDF, Criminal IP, alphaMountain.ai, CyRadar and Chong Lua Dao. That is a solid minority of independent vendors, which means many browsers and security tools will already warn users. Most engines still do not flag it, so some visitors will reach the page without any warning. PhishDestroy lists the domain on its blocklist.

Infrastructure

The page sits on a subdomain of zapier.app, a shared platform domain registered on 2022-09-20 through Name.com, Inc. That date belongs to the platform, not to this phishing page. The scammers borrowed an established, trusted parent domain instead of registering their own lookalike, which helps the page slip past filters that look for newly registered domains. Hosting resolves to Amazon.com, Inc. infrastructure in the US. The Let's Encrypt certificate only means the padlock appears and says nothing about legitimacy.

What to do

If you entered your Ledger recovery phrase on this page, treat the wallet as compromised. Set up a new device or a freshly generated seed and move any remaining funds to it right away, since the attacker can act at any moment. Never reuse the exposed phrase, and ignore any follow-up messages offering "recovery" help, which are often a second scam. Defenders should block the full subdomain, report it to Zapier for removal, and remind users that Ledger never requests seed phrases online.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 2 captures

Observed page title
Forms
Certificado TLS
Emitido por Let's Encrypt / YR1 · stored validity ends in 30 days

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
IP Context Vercel shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
Registrar (base domain) Name.com US(US)
Contacto de abuso["abuse@name.com"]
Registro de la ICANNICANN Lookup (RDAP) →
Registration (base domain)zapier.app · Creado 20/09/2022 — Expires 20/09/2027
Estado HTTP308 Permanent Redirect
Detalles técnicosProvenance & timestamps
Primera detección06/09/2026
DOM Analysisanalyzed 09/10/2026score 88/100
Favicon Hash
ICANN OVERSIGHT Registration: zapier.app

Acreditación y contexto RAA

Registrar accreditation and DNS abuse obligations

For the registrable domain zapier.app behind this subdomain, 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.

Accountability draft No se envía nada automáticamente.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.239.123.129
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

La reputación de Edge-IP no se atribuye a este dominio.

Servidores de nombres 1

  • ns2.vercel-dns.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YR1
Valid from
2026-08-22 02:51:05
Valid until
2026-11-20 02:51:04
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:29 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta813a4e503b35535fb96a4c8df328eb445fdbba2e1686ddb446de1bec037f88f

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 10:06:19 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-20 10:06:19 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-20 10:06:19 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 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

15 / Los proveedores de seguridad de 89 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 15 detections
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE
Webroot
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

hoomepage-ledger.zapier.app
Resultado guardado
Cloaked / Filtered
Stored observation history21

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Desconocido→protected

    http_access_restricted · access_restriction

  3. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

Earlier observations 16
  1. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Desconocido→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  5. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Desconocido→protected

    http_access_restricted · access_restriction

  7. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  8. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  11. Availability monitor · Recorded state

    No disponible→Accesible

  12. Availability monitor · Recorded state

    Desconocido→inactive

    http_no_content

  13. Availability monitor · Recorded state

    Desconocido→inactive

    http_no_content

  14. Availability monitor · Recorded state

    Desconocido→inactive

    http_no_content

  15. Availability monitor · Recorded state

    Accesible→No disponible

  16. Availability monitor · First collection record

    Accesible

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    15/89 engine detections

    View source
  3. Added to PhishDestroy

    hoomepage-ledger.zapier.app

    View source

Dominios similares

151 dominios similares almacenados

Mostrar todo (88)
eldger.com transposition kedger.com replacement kledger.com insertion l3dger.com replacement ldeger.com transposition ldger.com omission le.dger.com subdomain lecger.com replacement ledber.com replacement ledegr.com transposition leder.com omission ledg3r.com replacement ledge.com omission ledged.com replacement ledgedr.com insertion ledgee.com replacement ledgeer.com repetition ledgercom.com various ledget.com replacement ledgewr.com insertion ledgger.com repetition ledgir.com vowel-swap ledgor.com vowel-swap ledgr.com omission ledgre.com transposition ledgrer.com insertion ledgsr.com replacement ledgwer.com insertion ledgwr.com replacement ledher.com replacement ledhger.com insertion ledsger.com insertion ledtger.com insertion ledyer.com replacement ledzer.com replacement leedger.com insertion legder.com transposition leger.com omission lerdger.com insertion lerger.com replacement lesger.com replacement lewdger.com insertion lidger.com vowel-swap lledger.com repetition lodger.com vowel-swap lrdger.com replacement lsdger.com replacement oedger.com replacement pedger.com replacement pledger.com insertion dedger.com bitsquatting hedger.com bitsquatting iedger.com homoglyph l-edger.com hyphenation ladger.com bitsquatting lcdlger.com homoglyph lddger.com bitsquatting lebger.com homoglyph leclger.com homoglyph ledcer.com bitsquatting leddger.com insertion ledeer.com bitsquatting ledeger.com insertion ledfer.com bitsquatting ledg-er.com hyphenation ledgar.com bitsquatting ledger0.com addition ledger1.com addition ledger4.com addition ledger5.com addition ledger6.com addition ledgerb.com addition ledgerc.com addition ledgerf.com addition ledgeri.com addition ledgern.com addition ledgerq.com addition ledgerx.com addition ledges.com bitsquatting ledgez.com bitsquatting ledgur.com bitsquatting lediger.com homoglyph ledqer.com homoglyph leeger.com bitsquatting leelger.com homoglyph lefger.com bitsquatting letger.com bitsquatting ludger.com bitsquatting

Se muestran 100 de 151

Datos y informes externos

Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

3 evidence signal groups linked 0 stored notification records Último activo conocido

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Official reporting routes

¡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 →

Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

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
After a phishing incident

Recomendaciones y consejos para las víctimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

¿Qué debo hacer ahora mismo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos hoomepage-ledger.zapier.app)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/hoomepage-ledger.zapier.app"
  title="PhishDestroy threat report for hoomepage-ledger.zapier.app"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>