On 2026-10-01, akt1sportstore.shop returned an HTTP 502 status when checked, indicating a server-side error at that time. The domain was also included in the publisher-owned PhishDestroy internal catalogue, highlighting additional scrutiny from security sources.
Recorded Evidence
A VirusTotal scan on 2026-09-29 found 16 detections out of 91 scanners for akt1sportstore.shop. OTX, checked on 2026-09-29, recorded 2 pulses referencing the domain. The domain was registered through Spaceship, Inc. on 2026-03-26, and its first observation in this evidence set was on 2026-09-26. The HTTP check on 2026-10-01 recorded a 502 status code.
Interpretation
These records from VirusTotal, OTX, and PhishDestroy each provide distinct perspectives on akt1sportstore.shop, reflecting different types of monitoring and detection. The HTTP 502 response documents a specific server error on one date, while the catalogue listing and scanner results indicate the domain has drawn attention from multiple security sources. The registration and observation dates offer context for the timing of these findings.
Recommended Actions
Review and retain the VirusTotal, OTX, and PhishDestroy records for akt1sportstore.shop for future reference and comparison. Examine the HTTP 502 response alongside these security listings to inform any further action regarding the domain. Consider each source's findings separately to ensure a comprehensive evaluation.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
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:42:14 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-09-27 04:28:45 UTC
VirusTotal scanner detections updated from 15 to 16. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 22:00:27 UTC
VirusTotal scanner detections updated from 16 to 15. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 08:55:31 UTC
VirusTotal scanner detections updated from 15 to 16. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-26 05:15:35 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.244.119.61.
威胁响应 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.
(US)
