Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
facebook-verification-badge.com favicon

facebook-verification-badge.com

“404: NOT_FOUND”

Registrador
Name.com
Resolved IP
64.29.17.65
Registered
23/06/2026
PhishDestroy assessment Crítico
Disponibilidad Último activo conocido Anteriormente no disponible; la última observación fue alcanzable Observado · HTTP probe
VirusTotal detecciones: 17/89 Spamhaus DBL: DBL_PHISH Etiqueta automática de marca: Facebook
OTX: 4 refs 06/09/2026 CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 17. Tenga extrema precaución: no ingrese credenciales o información personal.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Resumen del informe

Suplantación de Facebook: facebook-verification-badge.com — Último activo conocido (HTTP 308). Resumen de las pruebas: VirusTotal 17/89 (Criminal IP…

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

Source evidenceVirusTotal 17 / 89 · OTX 4 references 6 sources

VirusTotal

17 / 89 engine detections

Abrir informe

Spamhaus DBL

DBL_PHISH

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
17 / 89
OTX
4 community refs
Page captures
2

PhishDestroy threat report

Overview

facebook-verification-badge.com is an impersonation phishing site built around the Facebook brand. Its name targets page owners, creators and businesses who want the blue verification badge. PhishDestroy first flagged it on 2026-09-06. As of 2026-10-19 the domain was still alive and answering requests with a redirect, so it remains usable for phishing.

How the scam works

Badge-themed phishing usually starts with a message warning that a page will be restricted, or offering verification if the owner confirms their details. The victim is sent to a lookalike Facebook form that asks for login credentials, two-factor codes and sometimes ID documents or payment details. The attackers then take over the account, lock out the owner, and use the page for scams or resell it. The page title currently reads "404: NOT_FOUND", while we classify the domain as a Facebook impersonation phishing page.

Evidence

When VirusTotal last checked on 2026-09-17, 17 of 89 security engines flagged the domain. Those engines included BitDefender, ESET, Forcepoint ThreatSeeker, Criminal IP, alphaMountain.ai, CRDF, CyRadar and the Vietnamese anti-scam project Chong Lua Dao. That is broad agreement across unrelated vendors. Spamhaus lists the domain on its DBL with a phishing designation, which blocks it in many mail filters. It also appears in 4 AlienVault OTX threat pulses and on the PhishDestroy blocklist.

Infrastructure

The domain was registered through Name.com, Inc. on 2026-06-23, about 75 days before PhishDestroy detected it. That gap suggests it was set up in advance rather than used the moment it was registered. It resolves to an address on Amazon's network in the United States. Large cloud hosting like this lets operators move or rebuild a site quickly.

What to do

Facebook does not grant verification through outside websites, so treat any badge offer that leads here as fraudulent. If you entered your Facebook login, change the password right away and also change it anywhere else you reused it. Turn on or reset two-factor authentication, log out all unknown sessions in Security settings, and check that your recovery email and phone number are still yours. If you lost access, use Facebook's official hacked-account recovery flow. If you submitted ID or card details, contact your bank and watch for identity fraud. Security teams should block the domain at DNS and mail gateways, enforce the Spamhaus DBL listing, and warn social media managers about badge-verification lures.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 2 captures

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.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodominiosdrainerfraudmonthlyphishdestroyphishingscam
Registrador Name.com US(US)
Contacto de abuso["abuse@name.com"]
Registro de la ICANNICANN Lookup (RDAP) →
RegistroCreado 23/06/2026 (119d) — Expires 23/06/2027
Estado HTTP308 Permanent Redirect
Elapsed Since First Report 43 days
Qué contabilizamos Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Último activo conocido.
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ón06/09/2026
DOM Analysisanalyzed 09/10/2026score 98/100
Favicon Hash
Observed page title
404: NOT_FOUND
Certificado TLS
Emitido por Let's Encrypt / YR1 · stored validity ends in 33 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.29.17.65
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-25 04:56:37
Valid until
2026-11-23 04:56:36
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:44 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8dba1140a9554ccd5a6141b6644533f388852c21e7dbb24b8d7121d64a9d9605

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-19 22:35:00 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-19 22:35:00 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-19 22:35:00 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
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

17 / Los proveedores de seguridad de 89 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 17 detections
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
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.

Stored observation history23

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

    Accesible→No disponible

  2. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

Earlier observations 18
  1. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    No disponible→Accesible

  3. Availability monitor · Recorded state

    Accesible→No disponible

  4. Availability monitor · Recorded state

    Desconocido→protected

    http_access_restricted · access_restriction

  5. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  6. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Desconocido→protected

    http_access_restricted · access_restriction

  8. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  9. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  10. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  11. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  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

    Desconocido→inactive

    http_no_content

  16. Availability monitor · Recorded state

    No disponible→Accesible

  17. Availability monitor · Recorded state

    Accesible→No disponible

  18. Availability monitor · First collection record

    Accesible

Recorded activity

4 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    17/89 engine detections

    View source
  4. Added to PhishDestroy

    facebook-verification-badge.com

    View source

Check for cloaking

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

facebook-verification-badge.com

Datos y informes externos

Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

4 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 facebook-verification-badge.com)
  • 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/facebook-verification-badge.com"
  title="PhishDestroy threat report for facebook-verification-badge.com"
  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>