berryhaven.shop was first observed on 2026-10-13, with a record from that date documenting its presence in the PhishDestroy internal listing. The domain also has a PageSpeed performance score of 56 recorded on the same day, providing insight into its technical profile.
Recorded Evidence
VirusTotal checked berryhaven.shop on 2026-10-11, recording 5 detections out of 92 total scanners. OTX referenced the domain with three pulses on 2026-10-13. The PhishDestroy internal listing included the domain as of 2026-10-13. PageSpeed recorded a performance score of 56 for berryhaven.shop on 2026-10-13.
Interpretation
The VirusTotal record contains a measurement of how many security scanners detected issues with berryhaven.shop, offering a snapshot of its security profile at the time of observation. The PhishDestroy internal listing documents the domain's inclusion in a publisher-managed catalogue, while OTX records its presence in three intelligence pulses, reflecting external attention. These sources together provide a multi-faceted view of the domain's recorded status without asserting any current condition.
Recommended Actions
For berryhaven.shop, retain the VirusTotal, PhishDestroy, and OTX records as references for future comparison. Compare the PageSpeed performance score with subsequent technical assessments to monitor any changes. Continue to review new evidence as it becomes available to maintain an up-to-date profile of the domain's recorded observations.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 07:28:10 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 07:28:10 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.
Last analyzed Previous stored snapshot: 5 detections
CRDF
G-Data
Gridinsoft
LevelBlue
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of berryhaven.shop· checked Oct 13, 2026
56
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
5.13s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
499ms
Total Blocking Time
SI
6.84s
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:20:32 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 31.222.234.210.
Threat Response Pipeline
Discovery
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
berryhaven.shop detected and queued for full analysis
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.
5 evidence signal groups linked0 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · berryhaven.shop
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
