Ir al informe de seguridad
Domain security report
verify.captcha-bot.digital favicon

verify.captcha-bot.digital

“NSFW Content”

Veredicto de amenaza
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilidad Contenido no disponible El contenido no estaba disponible en la última observación. Observado · HTTP probe
VirusTotal detecciones: 1/95 Automated brand label: ["discord"]
04/12/2025 ["discord"] CDN
API
Registrador
Cloudflare
Resolved IP
172.67.70.247
2 sources
In this reportGet help
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 1. Tenga extrema precaución: no ingrese credenciales o información personal.
Resumen del informe

verify.captcha-bot.digital — Contenido no disponible. Suplantación de marca: ["discord"]; Tipo de estafa: Credential Phishing. Resumen de las pruebas: VirusTotal 1/95 (SOCRadar); PhishDestroy score 61/100. Registrador: Cloudflare.

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

Additional indicators at a glance

VirusTotal
VirusTotal
1 det.
URLScan
URLScan
Estado observado
Contenido no disponible
PhishDestroy
DestroyList
Incluido

Source evidence

7 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

1 / 95

Denunciar
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

OTX

no community references

Denunciar
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

informe almacenado

View stored capture ↗
Denunciar
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Análisis finalizado

Denunciar
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Detalles
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Resumen de las pruebas

Alto
VirusTotal
1/95
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

The domain verify.captcha-bot.digital was involved in a generic phishing or scam operation and is currently down, indicating a potential takedown. This domain did not impersonate a specific brand, instead operating as an unbranded scam.

One out of 95 security vendors on VirusTotal flagged verify.captcha-bot.digital as malicious, specifically SOCRadar. The domain appears on one public blocklist. Google Safe Browsing has not flagged this domain.

Cloudflare, Inc. (US) registered the domain, which resolved to the hosting IP address 172.67.70.247. This domain was first seen on 2025-12-04.

Block verify.captcha-bot.digital and its associated IP 172.67.70.247 at the perimeter, noting the site's current down status.

Data coverage & collection

18 · datasets with records / 13 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
1 / 95 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
limpioCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Cloudflare, Inc.Collection time not recorded
Network & DNS
172.67.70.247 · 0 · nameserversCollection time not recorded
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Availability history
14 · stored state changes
Source observation history
3 · stored source events
Reportes de la comunidad
Aggregate report counts and dates
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 13

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Certificado TLS
  • HTML archives
  • Site configuration files
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Estado de la lista de bloqueados pública

Domain, network & archive

Cloudflare, Inc. · 172.67.70.247 · DNS, TLS and retained responses

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
Registrar (base domain) Cloudflare US(US)
Contacto de abusoabuse@verify.captcha-bot.digital
Registro de la ICANNICANN Lookup (RDAP) →
Tiempo hasta la primera indisponibilidad 81 days
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ón04/12/2025
DOM Analysisanalyzed 29/07/2026score 61/1001 brand signal
Submitted URLhttps://verify.captcha-bot.digital/verify?… query redacted
ICANN OVERSIGHT Registration: captcha-bot.digital

Acreditación y contexto RAA

Registrar accreditation and DNS abuse obligations

For the registrable domain captcha-bot.digital 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
172.67.70.247
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

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

Location describes the IP network.

Latest Classified Outcome 2026-10-14 20:21:26 UTC

Primary outcome DNS inactivo reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Desconocido Probe Inconclusive 20% 2026-10-15 01:09:37 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-02-14 16:35:24 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-02-14 16:35:24 UTC → 2026-09-30 16:14:55 UTC · 5,471.66h midpoint estimate ≈ 2026-06-08 16:25:09 UTC · precision very 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 · 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

1 / Los proveedores de seguridad de 95 marcaron este dominio
View on VT
Last analyzed
SOCRadar

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
5471.66
Estimate basis
Bounded by observations
Estimate precision
very_low

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

Detection & evasion checks

Stored browser and crawler observations

Análisis de detección y evasión

Comprobación del enmascaramiento y la distribución del tráfico

Aún no se ha escaneado Aú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='verify.captcha-bot.digital', port=80): Max retries exceeded with url: / (Caused by NewConn

Comprobación de huellas dactilares en directo en TDS
Siete indicadores de Keitaro y una comparación entre navegador y rastreador. El análisis comienza solo al pulsar el botón.
Resultado guardado
Inaccesible

Timeline & response

Collection history, report status and investigation channels

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.
  1. Cloudflare Radar Scan 2026-03-07 11:51:54 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
  2. Cloudflare Radar Scan 2026-03-07 06:07:11 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
  3. Domain Status Transition 2026-02-28 01:40:19 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
Stored observation history17

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

    dns_inactive→Desconocido

    probe_inconclusive

  2. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Desconocido

    probe_inconclusive

  4. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Desconocido

    probe_inconclusive

Earlier observations 12
  1. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Desconocido

    probe_inconclusive

  3. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Desconocido

    origin_unreachable · http_5xx

  5. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive→Desconocido

    origin_unreachable · http_5xx

  7. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive→Desconocido

    origin_unreachable · http_5xx

  9. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/e46601da-54e6-4a5b-bf7b-45f441f99a69

  11. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/833e41d1-a1d5-425b-a085-12b01afbb60c

  12. Availability monitor · Recorded state

    Accesible→No disponible

Proceso de respuesta ante amenazas Pipeline

Descubrimiento
Analysis
Monitoring

14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Amenaza detectada
verify.captcha-bot.digital detectados y puestos en cola para su análisis completo
04/12/2025
URLScan.io Capture
Almacenado URLScan report with capture artifacts
27/02/2026
Cloudflare Radar Report
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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
14/03/2026
VirusTotal
1/95 recorded on VirusTotal
23/02/2026
Brand Impersonation
Impersonation of ["discord"]
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
27/02/2026
Technical Analysis Recorded
El informe contiene tecnología almacenada o resultados de análisis forenses.
16/10/2026
Cloudflare Radar Scan
Escaneado con Cloudflare Radar; análisis de red completado.
07/03/2026
Cloudflare Radar Scan
Escaneado con Cloudflare Radar; análisis de red completado.
07/03/2026
Content Observed Unavailable
El monitoreo registró una respuesta no disponible (HTTP 404); la causa no se estableció de forma independiente.
28/02/2026
Lista de destrucción publicada
04/12/2025
Content Observed Unavailable
Las últimas comprobaciones almacenadas indican que el contenido informado no está disponible; esto no establece quién o qué causó el cambio.
23/02/2026
Tiempo hasta la primera indisponibilidad
1943 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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Reportes de la comunidad

Reportado por 1 miembro de la comunidad; visto por primera vez el 04/12/2025

Reportes almacenados
1
URL únicas reportadas
1
Aceptado1

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

¿Te ha afectado esta página web?

3 evidence signal groups linked 0 stored notification records Contenido no disponible

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 verify.captcha-bot.digital)
  • 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
Read the evidence in context

Acerca de este informe: verify.captcha-bot.digital

Este informe presenta la última evidencia almacenada disponible para PhishDestroy. Las marcas de tiempo de origen se muestran cuando están disponibles; La disponibilidad y los veredictos de los proveedores pueden cambiar después de la recolección.

El sitio capturado mostraba el título de la página “NSFW Content” y puede estar haciéndose pasar por ["discord"].

A partir de 2026-02-23 07:04:30 UTC, verify.captcha-bot.digital tuvo detecciones de los motores de seguridad 1.

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A 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/verify.captcha-bot.digital"
  title="PhishDestroy threat report for verify.captcha-bot.digital"
  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>