VirusTotal
12 / 92
“Motorsport Data Acquisition”
On 2026-10-01 aimshophq.shop returned an HTTP 301 status, a dated server response that does not by itself establish present availability. A PageSpeed performance score of 83 was recorded for the domain on 2026-09-25, giving a separate front-end measurement from that earlier date.
The PhishDestroy internal listing for aimshophq.shop was recorded on 2026-09-25. VirusTotal reported 11 detections across 91 scanners on 2026-09-28. OTX showed 4 pulses on 2026-09-27. An SSL certificate issued by Let's Encrypt / YE1 was scanned on 2026-09-25. The domain first appeared in these records on 2026-09-25.
The PhishDestroy listing, the VirusTotal result and the OTX count were captured on different dates, so their values describe separate moments rather than one synchronized view. Because the PageSpeed and SSL scans share a date while the VirusTotal and OTX checks fall later, comparisons across sources should account for that gap. The dated HTTP response likewise reflects only the moment it was recorded.
Anyone reviewing aimshophq.shop should preserve the dated records cited here alongside any later observations of the same domain. When new scans become available, compare them against these dates and values rather than treating any single result as current. During review, avoid submitting personal or sensitive information to the site.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
CaddyScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://aimshophq.shop/; server=Caddy
glen.ns.cloudflare.comkelly.ns.cloudflare.comLocation describes the IP network.
7674a1c348a6c8bb76f3369a592445d6139dd012e3cb527d43ef5e969ae4a003Saved 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 aimshophq.shop · checked Sep 25, 2026
195.96.130.212. 14 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