VirusTotal
3 / 89
perc.exchange — Encoberto · alcançável (HTTP 403). Representação da marca: Google; Tipo de golpe: Generic Phishing. Resumo das evidências: VirusTotal 3/89 (alphaMountain.ai, Fortinet, Gridinsoft); URLQuery 3 alerts; Spamhaus DBL_PHISH; cloaking observed; PhishDestroy score 96/100. Registrador: NiceNIC.
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | perc.exchange |
malicious | Sinkholed |
| DNS4EU | perc.exchange |
malicious | Sinkholed |
| DNS4EU | percdex.net |
malicious | Sinkholed |
The domain perc.exchange was registered on April 04, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED and is currently active. DNS resolution points to the Cloudflare‑owned address 172.67.147.63, serviced by the authoritative nameservers nile.ns.cloudflare.com and ollie.ns.cloudflare.com, and the site presents a TLS certificate issued by Let’s Encrypt (identifier YE1). HTTP requests return a 403 status and the only observed page title is "Just a moment...", indicating that the content has not been publicly disclosed. Threat intelligence sources show that six of ninety‑four VirusTotal scanners flagged the domain, and eight AlienVault OTX pulses reference it, suggesting a pattern of abuse. The domain appears on one external blocklist and has been blocked by the PhishDestroy feed; a Gridinsoft trust score of 0 / 100 further reflects low reputation. The infrastructure is linked to a Google brand impersonation campaign, classifying the risk as high. While the exact payload or credential‑collection mechanism remains unknown, defenders should treat perc.exchange as hostile, add the domain and its IP to network‑level deny lists, monitor DNS queries for related indicators, and ensure that any email or web filtering solutions are updated to block traffic to this host.
A página exibia uma resposta para um visitante que parecia um navegador e outra para um rastreador ou um verificador de segurança. O cloaking existe apenas para impedir que os avaliadores tenham acesso à página de destino real.
bot_redirect_safecloudflareNota do digitalizador: cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
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.
A reputação do Edge-IP não é atribuída a este domínio.
ollie.ns.cloudflare.comLocation describes the IP network.
a8922bd94cd58282ad2ab22edf381319e88d4bb9015f4802b47fbaf135c82cfaSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Denunciado por 1 membro da comunidade; visto pela primeira vez em 04/04/2026
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.
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
Template-based draft · optional AI wording assistance requires separate consent
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraEnvie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarRelatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMonitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo