The domain aimnsportswear.shop was included in the PhishDestroy internal listing as of 2026-10-01, according to publisher records. OTX also recorded activity related to the domain by that date.
Recorded Evidence
PhishDestroy listed aimnsportswear.shop internally on 2026-10-01. VirusTotal recorded 0 detections out of 91 scanners on 2026-10-01. OTX registered two pulses for the domain by 2026-10-01. The domain was registered with Dynadot Inc. on 2026-06-04.
Interpretation
These records provide a snapshot of how aimnsportswear.shop appeared in multiple monitoring sources on and before 2026-10-01. The presence in both the PhishDestroy internal listing and OTX pulses shows that the domain was noted by more than one monitoring platform. VirusTotal's scan on the same date did not yield any detections, which is a technical observation from that specific scan.
Recommended Actions
For continued review of aimnsportswear.shop, preserve the PhishDestroy internal listing, VirusTotal scan results, and OTX pulse records. Compare these dated records with future monitoring findings to track any changes. Reference each source's entries directly for ongoing evaluation.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 10:44:10 UTC
RDAP registration未知
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.
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-10-01 18:46:19 UTC
VirusTotal scanner detections updated from 6 to 0. Resolved alerts: CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar, alphaMountain.ai.
VirusTotal Detections Update2026-09-26 13:47:04 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 02:51:04 UTC
VirusTotal scanner detections updated from 6 to 5. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 02:19:27 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-09-25 07:03:19 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 04:54:32 UTC
VirusTotal scanner detections updated from 4 to 4. Added scanner alerts: Forcepoint ThreatSeeker. Resolved alerts: LevelBlue.
Threat First Observed2026-09-25 01:58:34 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.245.239.118.
威胁响应 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.
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月1日
Brand Impersonation
Impersonation of Fakeshop
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(US)
