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.
Recorded Evidence
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.
Interpretation
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.
Recommended Actions
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:31:12 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:31:12 UTClast content: 2026-10-11 10:31:12 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
使用技術 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Google PageSpeed Insights — mobile performance audit of aimshophq.shop· checked Sep 25, 2026
83
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
3.6s
Largest Contentful Paint
CLS
0.013
Cumulative Layout Shift
TBT
173ms
Total Blocking Time
SI
2.89s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-27 13:05:40 UTC
VirusTotal scanner detections updated from 8 to 0. Resolved alerts: Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, Netcraft, SOCRadar, alphaMountain.ai.
VirusTotal Detections Update2026-09-25 09:53:43 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 07:03:17 UTC
VirusTotal scanner detections updated from 7 to 7. Added scanner alerts: Forcepoint ThreatSeeker. Resolved alerts: Fortinet.
Threat First Observed2026-09-25 02:01:46 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.212.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
