Ir para o relatório de segurança
Domain security report
getsecurecard.com favicon

getsecurecard.com

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

Veredicto de ameaça
Assessment sources

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

Disponibilidade Não verificado A acessibilidade atual não foi verificada Observado · HTTP probe
Correspondências da lista de bloqueio armazenada: 2 Automated brand label: MetaMask Domínio jovem: 2 dias atrás
OTX: 4 refs 16/10/2026 MetaMask 1 Report Sent CDN
API
Registrador
NameCheap
Resolved IP
64.29.17.1
Registered
15/10/2026
2 sources
Redirect recorded in the HTML archive→ www.getsecurecard.comView the dated response and saved headers
In this reportGet help
Este domínio foi sinalizado como malicioso
Listas de bloqueio públicas relatando uma correspondência: 2. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
ABUSE NOTICE · 24H+ 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; 40 hours 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
40 hours
Reports sent
1
Latest case ID
PD-20261016-19BBD0
Current status
Observed active at latest stored check
Resumo do relatório

getsecurecard.com — Não verificado. Representação da marca: MetaMask; Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 0/92; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 90/100. Registrador: NameCheap.

A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.

Additional indicators at a glance

OTX references
URLScan
URLScan
Certificado TLS
Within stored validity dates
Let's Encrypt / YR2 · Hostname coverage not recorded
Idade
2d Brand New!
PhishDestroy
DestroyList
Listado
Reports Sent
1

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.

Public blocklists

2 external matches

Detalhes
Interpretation & limits

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

VirusTotal

checked — no detections recorded

Denunciar
Interpretation & limits

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

OTX

4 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

relatório armazenado

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álise concluída

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.

Resumo das evidências

Crítico
OTX
4 community refs
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.

Assessment

getsecurecard.com was referenced on the MetaMask blocklist as of 2026-10-16, providing a dated entry that highlights its inclusion in external security monitoring. The domain was also observed in the SEAL blocklist, adding another layer of recorded external attention.

Recorded Evidence

MetaMask and SEAL both listed getsecurecard.com in their blocklists on 2026-10-16. VirusTotal checked the domain on 2026-10-16, recording 0 detections from 92 scanners. OTX documented four pulses referencing the domain on the same date. PhishDestroy included getsecurecard.com in its internal listing, and the domain was registered with NameCheap, Inc. on 2026-10-15.

Interpretation

PhishDestroy contains an internal listing for getsecurecard.com, which is a form of security intelligence record. VirusTotal provides a technical measurement by documenting how many scanners flagged the domain during its check. The presence of getsecurecard.com on both MetaMask and SEAL blocklists expands the scope of external monitoring captured in these records.

Recommended Actions

Retain the MetaMask, SEAL, PhishDestroy, and VirusTotal records for getsecurecard.com to support ongoing technical review. Compare OTX pulse counts and blocklist entries against future records to track changes in external security intelligence. Use these dated records to inform monitoring and future assessments of the domain.

Data coverage & collection

21 · datasets with records / 10 · 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
0 / 92 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
limpoCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
NameCheap, Inc.Collection time not recorded
Network & DNS
64.29.17.1 · 2 · nameserversCollection time not recorded
Certificado TLS
Let's Encrypt / YR2
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
4 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
Response records
1 · outgoing report records
Availability history
5 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Not recorded in this report 10

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
  • PageSpeed performance
  • Recorded subdomains
  • Denúncias da comunidade
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Status da lista de bloqueios pública

Domain, network & archive

NameCheap, Inc. · 64.29.17.1 · DNS, TLS and retained responses

Domain details

Domínio
URLScan verdict Análise concluída score 0 report ↗
IP Context Vercel shared edge origin IP hidden A reputação do Edge-IP não é atribuída a este domínio.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomíniosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador NameCheap US(US)
RegistroCriado 15/10/2026 (2d · Brand New!) — Expires 15/10/2027
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez16/10/2026
DOM Analysisanalyzed 16/10/2026score 90/1004 brand signals
Submitted URLhttp://getsecurecard.com/
Favicon Hash
ID do caso

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

A reputação do Edge-IP não é atribuída a este domínio.

Servidores de nomes 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
Hostname coverage
Hostname coverage not recorded
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-17 08:21:17 UTC

Primary outcome DNS inativo reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Desconhecido Probe Inconclusive 20% 2026-10-17 10:46:17 UTC
RDAP registration Desconhecido
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.
Cruzamento de inteligência de ameaças · 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 domínio Envie evidências e ajude a proteger outras pessoas
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.
Resposta
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
*
Idade
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.

Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
308
Observed at
2026-10-16 01:58:39 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
308
Observed at
2026-10-16 01:58:39 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
308
Observed at
2026-10-16 01:58:39 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

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
Médio

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álise de detecção e evasão

Verificação de cloaking e distribuição de tráfego

Ainda não foi digitalizado Ainda não foi registrada nenhuma diferença entre o rastreador e o navegador

Observações armazenadas comparando o rastreador com o navegador para este host, além de uma verificação em tempo real da assinatura digital para sistemas de distribuição de tráfego do tipo Keitaro.

Sinalizador de camuflagem armazenado
Ainda não foi digitalizado
Última varredura de camuflagem
Roteamento de captura
Local arquivado em 2026-10-16 01:58:39 UTC

Nota do digitalizador: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='getsecurecard.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr

Verificação de impressão digital “TDS” em tempo real
Sete indicadores do Keitaro e uma comparação entre navegador e rastreador. Uma nova análise começa somente ao pressionar o botão.
Sob demanda

Nenhum resultado desta verificação foi salvo.

Timeline & response

1 · outbound report records

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. Threat First Observed 2026-10-16 01:57:39 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 64.29.17.1.
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

    dns_inactive→Desconhecido

    probe_inconclusive

  2. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Desconhecido

    probe_inconclusive

  4. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Desconhecido

    probe_inconclusive

Earlier observations 1
  1. Availability monitor · First collection record

    Acessível

Pipeline de resposta a ameaças

Descoberta
Analysis
Notifications
Monitoring

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

Ameaça detectada
getsecurecard.com detectados e colocados na fila para análise completa
16/10/2026
URLScan.io Capture
Armazenado URLScan report with capture artifacts
16/10/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.
Detecção de lista de bloqueio
Encontrado em 2 blocklists: MetaMask, SEAL
17/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
16/10/2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
16/10/2026
Technical Analysis Recorded
O relatório contém tecnologia armazenada ou resultados de análises forenses.
17/10/2026
Sent Report Recorded
Stored outgoing record associated with registrar NameCheap, Inc., 2 abuse contacts
abuse@namecheap.comabuse@vercel.com
16/10/2026
Lista de Destruição Publicada
16/10/2026
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

Domínios semelhantes

79 domínios semelhantes armazenados

Mostrar tudo (67)
metasmask.io insertion Relatório interno metramask.io insertion Relatório interno mewtamask.io insertion Relatório interno mmetamask.io homoglyph Relatório interno mtamask.io omission Relatório interno mwetamask.io insertion Relatório interno nmetamask.io homoglyph Relatório interno metamark.io bitsquatting Relatório interno metamaskj.io addition Relatório interno metammask.io homoglyph Relatório interno metamnask.io homoglyph Relatório 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

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidências e relatórios externos

Instantâneo das evidências enviadas
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álise aprofundada

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Você foi afetado por este site?

4 evidence signal groups linked 1 stored notification records Não verificado
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Official reporting routes
Cuidado com os golpistas que prometem recuperação! Os criminosos podem entrar em contato novamente com as vítimas fingindo ser investigadores, advogados ou agentes de recuperação. Não pague taxas antecipadas nem compartilhe credenciais. Saiba mais sobre fraudes relacionadas à recuperação →
Notifique as autoridades locais

Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.

Diretório de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Rascunho assistido por IA – os detalhes do incidente são processados pelo provedor de IA · Revise e envie você mesmo
After a phishing incident

Recomendações e orientações para as vítimas

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

O que devo fazer agora mesmo?

Urgente

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

  • Alterar todas as senhas — e-mail, contas do Exchange, qualquer coisa que use a mesma senha
  • Ativar a autenticação de dois fatores usando um aplicativo autenticador (não por SMS). Desative a recuperação por SMS
  • Cartões de congelamento se você inseriu dados bancários no site de phishing

Que informações devo coletar para o meu relatório?

Diretrizes do 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.
  • Datas e horários exatos — de cada transação e do primeiro contato com o golpista
  • Capturas de tela — sites fraudulentos, mensagens de bate-papo, e-mails, transações em carteiras digitais, redes sociais
  • Todas as URLs e domínios utilizado pelo golpista (incluindo getsecurecard.com)
  • Comunicações — e-mails, mensagens de texto, números de telefone e nomes de usuário que o golpista utilizou

Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.

A quem devo denunciar o golpe?

  • FBI IC3 — Centro de Denúncias de Crimes na Internet (sistema federal de denúncias dos EUA)
  • Europol — Relatórios sobre crimes cibernéticos na Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polícia local — cria um registro oficial, mesmo que não possam agir imediatamente

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?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Abate de suínos — confiança construída ao longo de semanas pelo Telegram, WhatsApp e aplicativos de namoro; em seguida, o dinheiro foi roubado
  • Golpes relacionados à recuperação — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Golpes baseados em IA — deepfakes, phishing automatizado e sites gerados por IA, o que torna a fraude mais difícil de detectar

Como posso me proteger no futuro?

  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Verificar domínios — verificar PhishDestroy antes de interagir. Verifique se o site usa HTTPS, a ortografia e a idade do domínio
  • "Bom demais para ser verdade" = golpe — retornos garantidos, endossos de celebridades, prazos urgentes

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

Mantenha-se informado, mantenha-se seguro

Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo

Feed de ameaças em tempo real Recorrer deste anúncio
Read the evidence in context

Sobre este relatório: getsecurecard.com

Este relatório apresenta as últimas evidências armazenadas disponíveis para PhishDestroy. Os carimbos de data/hora de origem são mostrados quando disponíveis; a disponibilidade e os veredictos do fornecedor podem mudar após a coleta.

O site capturado exibia o título da página “The Cashless Era | The Evolution of Digital & Contactless Cards” e pode estar se passando por MetaMask.

PhishDestroy lista getsecurecard.com como suspeito. Foi verificado pelos mecanismos de segurança 92; veredictos automatizados podem mudar. O monitoramento continua. Observado: 2026-10-16 02:40:15 UTC

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

Incorporar este relatório

Compartilhe essas informações sobre ameaças em seu site ou blog

embed.html
<iframe
  src="https://phishdestroy.io/pt-br/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>