VirusTotal
13 / 89
“Site not found”
apphlxyztrade.netlify.app returned an HTTP 404 status on 2026-10-01, a recorded response from that day's check. The domain was first observed on 2026-09-14, and the PhishDestroy internal listing records it as present.
The HTTP check on 2026-10-01 recorded status 404 for apphlxyztrade.netlify.app. VirusTotal recorded 13 detections across 89 scanners on 2026-09-22. The PhishDestroy internal listing records the domain, and the first observation date is 2026-09-14. The IP address 63.176.8.218 is associated with AWS EC2 (eu-central-1) in DE.
The HTTP check, VirusTotal scan, and PhishDestroy listing are dated differently, so their records describe separate points in time rather than one consistent snapshot. Because the VirusTotal scan on 2026-09-22 and the HTTP check on 2026-10-01 were recorded on different dates, a reader can compare them only as distinct observations. The PhishDestroy listing and the first observation on 2026-09-14 provide additional dated reference points for that comparison.
Retain the dated records for apphlxyztrade.netlify.app, including the PhishDestroy listing, the VirusTotal result, and the HTTP response. Compare any subsequent observations against these records to identify changes over time. Avoid submitting sensitive information while reviewing apphlxyztrade.netlify.app.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
NetlifyScanner note: http_other: raw=http_404; http=404; via=http_proxy; server=Netlify
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
12 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