The domain bajestudioshop.shop was observed with a VirusTotal record dated 2026-09-29, which documents its detection by multiple scanners. Additionally, a PageSpeed performance score of 71 was recorded for this domain, providing insight into its technical profile at the time of review.
Recorded Evidence
VirusTotal checked bajestudioshop.shop on 2026-09-29 and recorded 5 detections out of 92 total scanners. The domain was also listed in the PhishDestroy internal catalogue as of 2026-10-10. A PageSpeed performance assessment was conducted on 2026-10-10, resulting in a score of 71. The first observation of this domain was also recorded on 2026-10-10.
Interpretation
VirusTotal provides a record of detections from a range of external scanners, capturing a snapshot of how bajestudioshop.shop was assessed by security engines on the specified date. The PhishDestroy listing documents its inclusion in an internal catalogue, which serves as a reference point for further review. These sources together offer a dated technical and security context for the domain, allowing for comparison across different types of recorded evidence.
Recommended Actions
For ongoing monitoring, retain the VirusTotal detection record for bajestudioshop.shop as a reference for future security assessments. The PhishDestroy listing should also be preserved to track any changes in internal catalogue status. Compare the PageSpeed performance score with subsequent technical reviews to observe any notable shifts in the domain's infrastructure or configuration.
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:00:20 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:20 UTClast content: 2026-10-11 10:00:20 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.
Google PageSpeed Insights — mobile performance audit of bajestudioshop.shop· checked Oct 10, 2026
71
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
5.86s
Largest Contentful Paint
CLS
0.032
Cumulative Layout Shift
TBT
165ms
Total Blocking Time
SI
2.99s
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-10 07:06:14 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.227.
脅威対応 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.
