arkelementshop.shop was observed returning an HTTP 301 status on 2026-10-08, which indicates a redirection response was recorded on that date. The domain was also included in the PhishDestroy internal catalogue, highlighting additional monitoring attention.
Recorded Evidence
VirusTotal recorded 6 detections out of 92 scanners for arkelementshop.shop on 2026-10-07. OTX reported 4 pulses related to this domain as of 2026-10-08. The page title was observed as 'The ARK Elements | The ARK elements' on 2026-10-07, and a PageSpeed performance score of 67 was recorded on the same day. The SSL certificate was issued by Let's Encrypt / YE1 as of 2026-10-07.
Interpretation
These records from VirusTotal, OTX, and the PhishDestroy internal catalogue provide several dated perspectives on arkelementshop.shop's monitoring and technical status. The evidence includes both security-related findings and technical characteristics, allowing for comparison across different sources. The combination of a recorded HTTP status, security detections, and catalogue listing illustrates the range of data collected about this domain within a brief timeframe.
Recommended Actions
For further review of arkelementshop.shop, it is advisable to preserve the records from VirusTotal, OTX, and the PhishDestroy internal catalogue. Comparing these source records alongside the dated HTTP response and performance data may help track any changes or developments related to the domain.
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:05 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:08:05 UTClast content: 2026-10-11 10:08:05 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: 6 detections
CRDF
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
ネットクラフト
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of arkelementshop.shop· checked Oct 7, 2026
67
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
15.08s
Largest Contentful Paint
CLS
0.015
Cumulative Layout Shift
TBT
206ms
Total Blocking Time
SI
3.01s
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 01:54:32 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: SOCRadar.
Threat First Observed2026-10-07 00:22:32 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.205.
脅威対応 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.
