Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
cardinghub.cm favicon

cardinghub.cm

“Cardinghub”

Registrador
Netcom.cm Sarl
Resolved IP
104.21.26.84
Registered
02/06/2026
PhishDestroy assessment Crítico
Disponibilidad Último activo conocido Última observación de accesibilidad almacenada Observado · HTTP probe
VirusTotal detecciones: 5/92 Etiqueta automática de marca: Bitget
OTX: 4 refs 16/10/2026 CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 5. 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 Bitget: cardinghub.cm — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 5/92 (alphaMountain.ai, CRDF, Forcepoint…

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

Source evidenceVirusTotal 5 / 92 · OTX 4 references 5 sources

VirusTotal

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

PhishDestroy threat report

Overview

cardinghub.cm is an impersonation phishing page that presents itself under the title "Cardinghub". It targets people looking for that name and steers them into handing over account details or money to an imitation site. PhishDestroy first saw the domain on 2026-10-16. As of 2026-10-19 the site is still alive and serving live content.

How the scam works

Impersonation pages copy the name and look of a known service so visitors believe they have reached the real one. A page branded "Cardinghub" typically asks visitors to register, log in, or deposit funds, often in cryptocurrency, before granting access. Anything entered goes to the operators. Credentials can be reused against other accounts, and deposits sent to the operators cannot be recovered. Victims lose their login details, any personal information they submit, and any payment they make.

Evidence

VirusTotal shows 5 of 92 engines flagging the domain as of 2026-10-19. The flagging vendors are alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That detection rate is low, so many security products will not yet block the site. The domain appears in 4 AlienVault OTX pulses and is listed on the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2026-06-02 through Netcom.cm Sarl under Cameroon's .cm country-code domain. It resolves to 104.21.26.84 on AS13335 (Cloudflare, Inc.), geolocated to the US, which means the origin server sits behind Cloudflare's proxy. Its TLS certificate was issued by Google Trust Services (WE1), so the padlock in the browser says nothing about whether the site is legitimate.

What to do

Do not register, log in, or send any payment on cardinghub.cm. If you entered a password there, change it right away on every service where you used it and turn on two-factor authentication. If you sent money or card details, contact your bank or payment provider immediately and keep any transaction references. Defenders should block the domain at the DNS and proxy level, watch logs for past visits, and report it to Cloudflare and the registrar so it can be taken down.

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 Cloudflare shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodominiosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Netcom.cm Sarl
Contacto de abuso["info@netcom.cm"]
Registro de la ICANNICANN Lookup (RDAP) →
RegistroCreado 02/06/2026 (139d) — Expires 02/06/2027
Estado HTTP200
Detalles técnicosProvenance & timestamps
Primera detección16/10/2026
DOM Analysisanalyzed 16/10/2026score 88/1007 brand signals
Submitted URLhttps://cardinghub.cm/
Favicon Hash
Observed page title
Cardinghub
Automated brand references
Bitget Chatgpt Ethereum Solana SushiSwap Uniswap Zerion
Certificado TLS
Emitido por Google Trust Services / WE1 · stored validity ends in 69 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.26.84
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.

Servidores de nombres 2

  • holly.ns.cloudflare.com
  • rodney.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Google Trust Services / WE1
Valid from
2026-09-29 19:31:56
Valid until
2026-12-28 20:31:52
Validity
Within stored validity dates
Collection time
2026-10-16 01:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprintb7affe78fd393fb0b6e8c6e15eaed5632fb2e3c5fa1ebe75f814fa6f5b30305c

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:46:20 UTC

Primary outcome Contenido activo reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenido activo Ordinary HTTP content served 90% 2026-10-19 22:46:20 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-19 22:46:20 UTC last content: 2026-10-19 22:46:20 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.cardinghub.cmDomain record

The original observation time is not recorded for these hostnames.

Tecnologías · 6 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

5 / Los proveedores de seguridad de 92 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of cardinghub.cm · checked Oct 16, 2026

99
Good
Performance
FCP
1.68s
First Contentful Paint
LCP
1.68s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.53s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://cardinghub.cm/
Cardinghub
Hub
Respuesta
HTTP 200
HTML body
74.8 KB
Compressed
14.3 KB
Links
95 internal · 1 external
Detected technologies
wordpresscloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 95f45afd371d5cdbd62c5abf7baa32a9ac74dbf07e5ee87156508f1c8aeb1c58
Open Graph title: Cardinghub
Open Graph description: Hub
Twitter card: summary
Saved response-header values · 15
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4b2fbc10f17d344-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Fri, 16 Oct 2026 00:35:25 GMT
Link
; rel="https://api.w.org/"
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=rO%2BVc0xbwK7GF%2Fd2sxGby8g8eK0cGyJ16pPZQlFu9G1iv9F4iE2gVO%2FAOEtFSOG%2F%2FaZBn89trhbOGIAVjPFfcW6JHu9kZCq%2BnSl7%2FsNlZhfDEndIgbjrRcZaaxyu8KTA"
Server
cloudflare
Speculation-Rules
"/cdn-cgi/speculation"
Transfer-Encoding
chunked
Vary
Accept-Encoding
x-turbo-charged-by
LiteSpeed

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content 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 history5

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

    content_served

  2. Availability monitor · Recorded state

    Desconocido→live_content

    content_served

  3. Availability monitor · Recorded state

    Desconocido→live_content

    content_served

  4. Availability monitor · Recorded state

    Desconocido→live_content

    content_served

  5. Availability monitor · First collection record

    Accesible

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    5/92 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Added to PhishDestroy

    cardinghub.cm

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

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

cardinghub.cm

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 cardinghub.cm)
  • 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/cardinghub.cm"
  title="PhishDestroy threat report for cardinghub.cm"
  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>