athwear.shop was observed returning an HTTP status 200 on 2026-10-08, confirming a successful response from the domain at that time. The domain was also recorded in the publisher-owned PhishDestroy internal listing, providing an additional catalogue reference.
Recorded Evidence
On 2026-10-08, athwear.shop produced an HTTP 200 response. VirusTotal checked the domain on 2026-10-07 and found 1 detection out of 92 scanners. OTX pulses were recorded as 3 on 2026-10-08. The domain was first observed on 2026-10-07 and a pagespeed performance score of 70 was measured on that date.
Interpretation
The available evidence from HTTP, VirusTotal, OTX, and PhishDestroy offers a multi-source view of athwear.shop’s technical and catalogue status. These dated records allow for comparison of response behavior and detection results without drawing conclusions about the domain’s content or intent. Chronological details from each source provide context for reviewing past observations.
Recommended Actions
To further assess athwear.shop, retain the HTTP response and VirusTotal detection records for ongoing reference. Compare OTX pulse counts and PhishDestroy listing status in future reviews. Preserve all dated evidence for subsequent analysis or monitoring, ensuring that each source’s observations remain available for comparison.
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-11 10:09:24 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:09:24 UTClast content: 2026-10-11 10:09:24 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.
Last analyzed First positive detection Previous stored snapshot: 1 detection
alphaMountain.ai
网站性能分析
Google PageSpeed Insights — mobile performance audit of athwear.shop· checked Oct 7, 2026
70
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
8.11s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
60ms
Total Blocking Time
SI
3.51s
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-10-07 20:29:43 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: alphaMountain.ai.
Threat First Observed2026-10-07 02:18:31 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.251.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
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)
