VirusTotal
5 / 92
comupex.com returned an HTTP 301 status on 2026-10-07, indicating a redirection response was recorded on that date. The domain was also included in the publisher’s PhishDestroy internal listing as of the same period.
On 2026-10-07, comupex.com was observed with an HTTP 301 status and a server header of 'cloudflare'. VirusTotal checked the domain on 2026-10-07, reporting 2 detections out of 92 scanners. OTX pulses included comupex.com in 3 separate instances as of 2026-10-07. The domain was registered through Fewmoretaps OU d/b/a Trustname.com on 2026-09-24, and its SSL certificate was issued by Let's Encrypt / YE1 as of 2026-10-07. A URLScan report was available from 2026-09-26.
The available evidence from HTTP, VirusTotal, OTX, and the publisher’s PhishDestroy listing provides multiple perspectives on comupex.com’s recent activity and security posture. The HTTP 301 status documents a redirect response at a specific point in time, while VirusTotal and OTX offer insight into how the domain has been perceived by security communities. The presence in the internal PhishDestroy listing and the availability of a URLScan report further expand the documented observations.
For comupex.com, retain the HTTP response records, VirusTotal scan results, OTX pulse references, and the PhishDestroy listing for ongoing review. Compare these records to future observations to monitor for any changes in status or security findings. Use the URLScan report as an additional reference point when evaluating the domain’s history and activity.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://comupex.com/; server=cloudflare
Edge-IP reputation is not attributed to this domain.
malavika.ns.cloudflare.comLocation describes the IP network.
7e19015af5f32fa444f8f4ae927ca0aac8fe9f753887528971e96b3dcf1e9e1aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
104.21.20.254. 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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive