The domain arianagrandecollection.shop was recorded by VirusTotal on 2026-09-27, where it was scanned by 91 engines and received five detections. A separate PageSpeed performance score of 65 was also documented on 2026-10-03, reflecting technical characteristics observed on that date.
Recorded Evidence
VirusTotal checked arianagrandecollection.shop on 2026-09-27, reporting five detections out of 91 scanners. OTX included the domain in four pulses as of 2026-10-03. On the same day, a PageSpeed performance score of 65 was recorded. The domain appeared in the PhishDestroy internal listing as of 2026-10-03.
Interpretation
These records show that arianagrandecollection.shop has been observed by multiple monitoring platforms, each providing data on different aspects of the domain. VirusTotal and OTX document attention from security-focused sources, while the PageSpeed score gives insight into technical performance. The PhishDestroy internal listing further indicates inclusion in a publisher-managed catalogue.
Recommended Actions
For ongoing evaluation of arianagrandecollection.shop, preserve the VirusTotal, OTX, and PhishDestroy records for future reference. Compare the PageSpeed performance data with later measurements to track any technical changes. Use these dated records as benchmarks when reviewing new observations about 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:37:41 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:37:41 UTClast content: 2026-10-11 10:37:41 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: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
G-Data
Gridinsoft
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of arianagrandecollection.shop· checked Oct 3, 2026
65
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
8.26s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
161ms
Total Blocking Time
SI
5.08s
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.
Threat First Observed2026-10-03 03:32:57 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.230.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 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.
