The domain atomstackstore.shop returned an HTTP 200 status code on 2026-10-08, confirming a successful web response at that time. It was also recorded in the PhishDestroy internal listing as targeting 'fakeshop'.
Recorded Evidence
On 2026-10-08, atomstackstore.shop responded with an HTTP 200 status code. VirusTotal reported 7 detections out of 92 scanners for this domain on 2026-10-07. OTX recorded 4 pulses as of 2026-10-08. The PhishDestroy internal listing identified the domain with the target brand 'fakeshop'. A PageSpeed performance score of 67 and a URLScan report were both recorded on 2026-10-07.
Interpretation
These records from VirusTotal, OTX, and PhishDestroy provide a multi-source view of atomstackstore.shop's observed status and attention from monitoring services. The HTTP response and PageSpeed score offer technical insight, while the internal listing and OTX pulses show the domain has been flagged for further scrutiny. The available URLScan report adds another layer of technical documentation for this domain.
Recommended Actions
To support ongoing review of atomstackstore.shop, retain the VirusTotal, OTX, and PhishDestroy records for future comparison. Preserve the PageSpeed and URLScan reports for technical reference. Use the HTTP 200 response as a point of comparison for subsequent web availability checks.
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:08:07 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:08:07 UTClast content: 2026-10-11 10:08:07 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: 7 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
ネットクラフト
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of atomstackstore.shop· checked Oct 7, 2026
67
Needs Work
Performance
FCP
2.91s
First Contentful Paint
LCP
7.22s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
120ms
Total Blocking Time
SI
4.72s
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-08 03:25:04 UTC
VirusTotal scanner detections updated from 8 to 7. Resolved alerts: SOCRadar.
VirusTotal Detections Update2026-10-07 23:20:53 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-10-07 20:12:11 UTC
VirusTotal scanner detections updated from 7 to 7. Added scanner alerts: SOCRadar. Resolved alerts: alphaMountain.ai.
VirusTotal Detections Update2026-10-07 02:08:42 UTC
VirusTotal scanner detections updated from 0 to 7. Added scanner alerts: CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft, LevelBlue, Netcraft, alphaMountain.ai.
Threat First Observed2026-10-07 01:03:08 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.219.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 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.
