Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
getsecurecard.com favicon

getsecurecard.com

“The Cashless Era | The Evolution of Digital & Contactless Cards”

Registrador
NameCheap
Resolved IP
64.29.17.1
PhishDestroy assessment Crítico
First observed Oct 16, 2026 01:57 UTC · PhishDestroy
VirusTotal detecciones: 5/92 Coincidencias de la lista de bloqueo almacenadas: 2 Etiqueta automática de marca: MetaMask
OTX: 4 refs 16/10/2026 1 Report Sent CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 5. Listas de bloqueo públicas que informan una coincidencia: 2. Tenga extrema precaución: no ingrese credenciales o información personal.
ABUSE NOTICE · 72H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@namecheap.com. The latest stored availability evidence still shows the domain reachable; 4 days 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.

Elapsed since first report
4 days
Reports sent
1
Latest case ID
PD-20261016-19BBD0
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Reports sent
view timeline
Resumen del informe

Suplantación de MetaMask: getsecurecard.com — No verificado. Resumen de las pruebas: VirusTotal 5/92 (ChainPatrol, CRDF, Forcepoint ThreatSeeker, SOCRadar…

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

getsecurecard.com is an impersonation phishing page that presents itself as a site about digital and contactless payment cards. It targets people looking for a secure card product, including crypto users. PhishDestroy first flagged it on 2026-10-16, one day after the domain was registered. At the last check on 2026-10-19 the server still responded, but the domain's DNS was inactive and the content was not being served.

How the scam works

The page carries the title "The Cashless Era | The Evolution of Digital & Contactless Cards", which reads like a neutral explainer, while PhishDestroy classifies the site as impersonation phishing. Pages of this type copy the look and language of a legitimate card or payment provider to win trust. They then push visitors toward an "apply" or "activate" step that asks for login credentials, card details, identity documents or a crypto wallet connection. Anything entered goes straight to the operators, who can take over accounts, make fraudulent charges or empty linked funds.

Evidence

Independent detection is still thin. VirusTotal returned 0 detections out of 92 engines on 2026-10-16, so a clean scan there should not be read as a sign of safety for a domain this new. The domain is listed on the PhishDestroy, MetaMask and SEAL blocklists, and it appears in 4 AlienVault OTX threat pulses.

Infrastructure

The domain was registered on 2026-10-15 through NameCheap, Inc. It is hosted on Amazon's network (AS16509, Amazon.com, Inc.) in the United States, at IP address 64.29.17.1. The site uses a free TLS certificate from Let's Encrypt (YR2), so the padlock in the browser only means the connection is encrypted. It says nothing about who runs the site.

What to do

Do not enter any personal, card or account information on getsecurecard.com. If you already did, contact your bank or card issuer to freeze or replace the card. Change any password you typed there and enable two-factor authentication on the affected accounts. Watch your statements for unfamiliar charges, and treat follow-up emails or messages that mention this card offer as further phishing. Security teams should block the domain and its IP at DNS and proxy level and add it to mail filters. They should also report it to the registrar and hosting provider so it stays offline if its DNS comes back.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Incluido View source
PhishDestroy PhishDestroy list View source
SEAL Incluido View source

Last checked

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-10activeall-domainsblocklistcontentcryptodominiosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador NameCheap US(US)
RegistroExpires 15/10/2027
Detalles técnicosProvenance & timestamps
Primera detección16/10/2026
DOM Analysisanalyzed 16/10/2026score 90/1004 brand signals
Submitted URLhttp://getsecurecard.com/
Favicon Hash
ID del caso
Observed page title
The Cashless Era | The Evolution of Digital & Contactless Cards
Automated brand references
Across Ledger Revolut Stripe
Certificado TLS
Emitido por Let's Encrypt / YR2 · stored validity ends in 84 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.29.17.1
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Walnut, US
Server header
Vercel

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

Servidores de nombres 2

  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-10-15 08:15:26
Valid until
2027-01-13 08:15:25
Validity
Within stored validity dates
Collection time
2026-10-16 04:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint45a7ade12c657f5b3553c4687cd986a86c832a82b7f55f305da203277adaac8a

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 08:34:10 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-19 22:46:21 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-16 01:57:39 UTC current episode first observed: 2026-10-16 08:21:12 UTC observed RIP window: 2026-10-16 01:57:39 UTC → 2026-10-16 08:21:12 UTC · 6.39h midpoint estimate ≈ 2026-10-16 05:09:25 UTC · precision medium · 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.
Cruce de inteligencia de amenazas · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
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: 0 detections
ChainPatrol
CRDF
Forcepoint ThreatSeeker
SOCRadar
VIPRE

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
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: http://getsecurecard.com/
Final URL: https://www.getsecurecard.com/
The Cashless Era | The Evolution of Digital & Contactless Cards
An educational research archive documenting the technological evolution of payment cards, EMV microchips, and modern contactless settlement.
Respuesta
HTTP 200
HTML body
47.9 KB
Compressed
10.5 KB
Links
11 internal · 0 external
Detected technologies
react
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Vercel
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: The Cashless Era | The Evolution of Digital & Contactless Cards
Open Graph description: An educational research archive documenting the technological evolution of payment cards, EMV microchips, and modern contactless settlement.
Twitter card: summary
Saved response-header values · 17
Access-Control-Allow-Origin
*
Edad
65134
Cache-Control
public, max-age=0, must-revalidate
Content-Disposition
inline
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 01:58:38 GMT
Etag
W/"b7f16de352d020e78bf6e86bed3c7f76"
Server
Vercel
Strict-Transport-Security
max-age=63072000
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
X-Matched-Path
/
X-Nextjs-Prerender
1
X-Nextjs-Stale-Time
300
X-Vercel-Cache
HIT
X-Vercel-Id
yul1::f2z4m-1792115918929-ff7ba709ccc9

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

Registration & observation details8

Availability observations

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

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

Stored observation history6

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

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Desconocido→dns_inactive

    dns_nxdomain

Earlier observations 1
  1. Availability monitor · First collection record

    Accesible

Recorded activity

6 entries
  1. VirusTotal

    5/92 engine detections

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Abuse report sent

    PD-20261016-19BBD0

    abuse@namecheap.com
  5. Added to PhishDestroy

    getsecurecard.com

    View source
  6. URLScan

    Page captured

    View source

Dominios similares

79 dominios similares almacenados

Mostrar todo (67)
metasmask.io insertion Informe interno metramask.io insertion Informe interno mewtamask.io insertion Informe interno mmetamask.io homoglyph Informe interno mtamask.io omission Informe interno mwetamask.io insertion Informe interno nmetamask.io homoglyph Informe interno metamark.io bitsquatting Informe interno metamaskj.io addition Informe interno metammask.io homoglyph Informe interno metamnask.io homoglyph Informe interno emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Check for cloaking

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

getsecurecard.com

Datos y informes externos

Instantánea de evidencia enviada
Sent: Ledger records: 1 Case ID: PD-20261016-19BBD0 Recipient: abuse@namecheap.com
PDF notice generated Notice text archived (289 chars)
Abuse notice text as sent to the provider
Registrar: Namecheap Inc (United States)
Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

5 evidence signal groups linked 1 stored notification records No verificado
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 getsecurecard.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/getsecurecard.com"
  title="PhishDestroy threat report for getsecurecard.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>