Ir para o relatório de segurança
Domain security report
x-security.org favicon

x-security.org

“X Security Holding — Преміум холдинг безпеки”

Veredicto de ameaça
Assessment sources

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

Disponibilidade Último ativo conhecido Última observação de acessibilidade armazenada Observado · HTTP probe
Detecções do VirusTotal: 13/91 Correspondências da lista de bloqueio armazenada: 2 Tipo de golpe: Impersonation
OTX: 16 refs 13/06/2026 CDN
API
Registrador
Internet Invest
Resolved IP
76.76.21.21
Registered
14/05/2026
2 sources
In this reportGet help
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 13. Listas de bloqueio públicas relatando uma correspondência: 2. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
Resumo do relatório

x-security.org — Último ativo conhecido (HTTP 307). Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 13/91 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Registrador: Internet Invest.

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

Additional indicators at a glance

VirusTotal
VirusTotal
13 det.
OTX references
URLScan
URLScan
Certificado TLS
Within stored validity dates
Let's Encrypt / YR2 · Hostname coverage not recorded
Idade
5 mo
Status observado
Último ativo conhecido 307
PhishDestroy
DestroyList
Listado

Source evidence

6 · 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

13 / 91

Denunciar
Interpretation & limits

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

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.

OTX

16 community references

Denunciar
Interpretation & limits

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

URLScan capture

relatório armazenado

View stored capture ↗
Observation time not recorded
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
VirusTotal
13/91
OTX
16 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.

Analysis of x-security.org shows a newly registered domain (created May 14, 2026) that resolves to the Vercel‑hosted IP 76.76.21.21 in the United States. The site presents the page title “X Security Holding — Преміум холдинг безпеки” and serves a valid Let's Encrypt R13 certificate, but returns an HTTP 307 redirect, suggesting an attempt to steer visitors to a secondary location. Infrastructure data lists five nameservers (nsa4.srv53.org, nsb3.srv53.org, nsc3.srv53.org, nsd3.srv53.org, nsa3.s...), indicating use of a shared DNS service. Reputation metrics are poor: Gridinsoft assigns a trust score of 0/100, the domain appears on three security blocklists, and it is actively blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal reports two detections out of 92 scanners, and AlienVault OTX references a single pulse linking the domain to malicious activity. The combination of a high‑risk classification, active blocklist listings, and recent registration points to a deliberate phishing operation, though the exact payload or targeted brand remains unverified because the page content has not been examined. Defenders should immediately block DNS resolution for x-security.org, add the domain to intrusion‑prevention and email‑filtering rules, and monitor for any related C2 traffic from the associated IP range. Continued observation of the nameserver set and any new detections is recommended to assess potential campaign evolution.

Data coverage & collection

16 · datasets with records / 15 · 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
13 / 91 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
16 · community references
External blocklists
2 · external matches
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Internet Invest, Ltd. dba Imena.uaCollection time not recorded
Network & DNS
76.76.21.21 · 1 · nameserversCollection time not recorded
Certificado TLS
Let's Encrypt / YR2
Page captures
2 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Availability history
31 · stored state changes
Denúncias da comunidade
Aggregate report counts and dates
IP reputation
Network-level observations
Not recorded in this report 15

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

  • URLQuery
  • PhishStats
  • Cloudflare Radar
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Source observation history
  • Lookalike relationships
  • 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

Internet Invest, Ltd. dba Imena.ua · 76.76.21.21 · 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-05activeall-domainsblocklistcontentcryptodomíniosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Internet Invest
Contato para abusos["abuse@imena.ua"]
Registro da ICANNICANN Lookup (RDAP) →
RegistroCriado 14/05/2026 (156d) — Expires 11/05/2027
Status HTTP307 Temporary Redirect
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez13/06/2026
DOM Analysisanalyzed 21/09/2026score 100/100
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
76.76.21.21
Network ASN
AS16509
Organization
Vercel, 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 1
  • nsc4.srv53.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-09-16 09:04:12
Valid until
2026-12-15 09:04:11
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-10 04:03:10 UTC
Collection source
PhishDestroy collector
Certificate fingerprint9c5f1b8ef092dc35b744b9677f98a08087f7198e0bbc44934ca6044171c4492f

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 22:35:30 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-17 22:35:30 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-17 22:35:30 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.
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

13 / Os fornecedores de segurança 91 sinalizaram este domínio
View on VT
Last analyzed Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
VIPRE
Webroot
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.

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

Não observado Não foi observado nenhum tipo de camuflagem na imagem digitalizada armazenada

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
Não observado
Pontuação de cloaking
0/6
Última varredura de camuflagem
Cabeçalho do servidor detectado pelo scanner
Vercel

Nota do digitalizador: redirect: raw=redirect_307; http=307; via=https_proxy; location=https://www.x-security.org/; server=Vercel

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.
Resultado salvo
Keitaro TDS

Timeline & response

Collection history, report status and investigation channels

Stored observation history31

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

    Desconhecido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  3. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  5. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

Earlier observations 26
  1. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  2. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  3. Availability monitor · Recorded state

    protected→Desconhecido

    probe_inconclusive

  4. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  5. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  6. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  7. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  8. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  9. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  10. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  11. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  12. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  13. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  14. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  15. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  16. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  17. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  18. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  19. Availability monitor · Recorded state

    redirected→Desconhecido

    stale_current_evidence

  20. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  21. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  22. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  23. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  24. Availability monitor · Recorded state

    redirected→Desconhecido

    probe_inconclusive

  25. Availability monitor · Recorded state

    Desconhecido→redirected

    http_redirect

  26. Availability monitor · Recorded state

    Desconhecido

    probe_inconclusive

Pipeline de resposta a ameaças

Descoberta
Analysis
Monitoring

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

Ameaça detectada
x-security.org detectados e colocados na fila para análise completa
13/06/2026
URLScan.io Capture
Armazenado URLScan report with capture artifacts
VirusTotal
13/91 recorded on VirusTotal
28/09/2026
Detecção de lista de bloqueio
Encontrado em 2 blocklists: MetaMask, SEAL
18/10/2026
OTX Community References
16 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
03/10/2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
O relatório contém tecnologia armazenada ou resultados de análises forenses.
18/10/2026
Lista de Destruição Publicada
13/06/2026
Monitoring Continues
O domínio permanece acessível ou com acesso restrito; verificações futuras poderão atualizar esta observação.
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

Denúncias da comunidade

Denunciado por 1 membro da comunidade; visto pela primeira vez em 14/05/2026

Denúncias armazenadas
1
URLs únicas denunciadas
1
Aceita1

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Você foi afetado por este site?

4 evidence signal groups linked 0 stored notification records Último ativo conhecido

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.

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 x-security.org)
  • 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: x-security.org

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 “X Security Holding — Преміум холдинг безпеки”.

A partir de 2026-09-28 02:30:55 UTC, x-security.org tinha detecções de mecanismos de segurança 13.

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/x-security.org"
  title="PhishDestroy threat report for x-security.org"
  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>