bbkperformanceshop.shop was observed with an HTTP status 200 on 2026-10-12, reflecting a successful recorded response from the domain at that time. The PageSpeed performance score of 81, measured on the same date, offers a technical snapshot of its optimization.
Recorded Evidence
VirusTotal recorded 1 detection out of 92 scanners for bbkperformanceshop.shop on 2026-10-11. OTX referenced the domain in 4 pulses as of 2026-10-12. The domain was internally listed by PhishDestroy, and its first observation was documented on 2026-10-11.
Interpretation
The VirusTotal record contains a scan-based detection measurement, providing a quantitative view of external security analysis. OTX offers community-driven intelligence entries through its pulse count. The HTTP status record documents a specific technical response, which can be used to track response behavior.
Recommended Actions
For bbkperformanceshop.shop, preserve the VirusTotal detection record and OTX pulse references for ongoing comparison. Retain the HTTP status response and PageSpeed performance score as technical benchmarks for future monitoring.
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-13 01:35:44 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 01:35:44 UTClast content: 2026-10-13 01:35:44 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
Gridinsoft
网站性能分析
Google PageSpeed Insights — mobile performance audit of bbkperformanceshop.shop· checked Oct 12, 2026
81
Needs Work
Performance
FCP
3.01s
First Contentful Paint
LCP
3.5s
Largest Contentful Paint
CLS
0.005
Cumulative Layout Shift
TBT
190ms
Total Blocking Time
SI
3.97s
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-12 09:22:23 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 146.19.203.210.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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)
