URLQuery
2 det.
“Home | Amacx Sports Nutrition”
PhishDestroy first observed amacxshop.shop on Oct 7, 2026. The captured page title is “Home | Amacx Sports Nutrition”. Current evidence score: 73/100 (critical).
One source contains a positive finding: URLQuery. URLQuery recorded 2 detections; no observation timestamp was retained. Additional recorded evidence: VirusTotal recorded 0 detections among 92 engines on Oct 7, 2026 at 04:47 UTC. AlienVault OTX listed 4 community pulse references (not vendor detections) on Oct 7, 2026 at 04:48 UTC. URLScan captured the page on Oct 7, 2026 at 03:42 UTC.
The collector marked the hostname reachable on Oct 7, 2026 at 03:42 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 7, 2026 at 01:42 UTC. At collection time, the hostname resolved to 46.245.239.84. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / YE2 as the certificate issuer with validity through Dec 31, 2026; checked Oct 7, 2026 at 04:02 UTC.
Stored content provides classification context alongside the positive source finding.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
hayes.ns.cloudflare.compiper.ns.cloudflare.comLocation describes the IP network.
1174af279c68b949a9bdaf09d8e4751466e4eefb699ce1b924e760e19292a54cSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of amacxshop.shop · checked Oct 7, 2026
46.245.239.84. 7 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