The domain berowear.shop is referenced in a PhishDestroy internal listing, with its presence recorded on 2026-10-13. A separate observation on the same date documents a PageSpeed performance score of 84 for the domain.
Recorded Evidence
VirusTotal checked berowear.shop on 2026-10-11, recording 15 detections out of 92 total scanners. OTX pulses included the domain in three separate entries as of 2026-10-13. A PageSpeed performance measurement was taken on 2026-10-13, and the PhishDestroy platform listed the domain internally on that same date.
Interpretation
The PhishDestroy record contains a listing event, which documents the domain's inclusion in its internal catalogue on a specific date. VirusTotal provides a quantitative measurement of detections from multiple scanners, offering a snapshot of how the domain was evaluated by various security engines. OTX records the domain's appearance in three pulse entries, reflecting its mention in threat intelligence feeds. These sources collectively provide a timeline and context for how berowear.shop has been referenced and assessed by different security platforms.
Recommended Actions
For berowear.shop, retain the VirusTotal detection record and the PhishDestroy internal listing as key evidence for ongoing monitoring. Compare future OTX pulse entries and PageSpeed performance scores to these stored records to track any changes in external intelligence or technical characteristics. Maintain a dated archive of all referenced source records for consistent review and analysis.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 07:24:54 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 07:24:54 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.
Google PageSpeed Insights — mobile performance audit of berowear.shop· checked Oct 13, 2026
84
Needs Work
Performance
FCP
2.87s
First Contentful Paint
LCP
3.46s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
111ms
Total Blocking Time
SI
3.98s
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-13 07:24:54 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 31.222.234.210.
威胁响应 Pipeline
发现
Analysis
Monitoring
7 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.
