perc[.]exchange
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.
Network Security Intelligence Registrar context
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | perc.exchange |
malicious | Sinkholed |
| DNS4EU | perc.exchange |
malicious | Sinkholed |
| DNS4EU | percdex.net |
malicious | Sinkholed |
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Latest Classified Outcome 2026-08-23 02:46:52 UTC
VirusTotal Analysis
Evidence & External Reports
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive