bencrest.shop is described in a 2026-10-13 VirusTotal observation, which recorded security detections for the domain. A PageSpeed performance score was also measured, providing additional technical context.
Recorded Evidence
VirusTotal documented 9 detections out of 92 scanners for bencrest.shop on 2026-10-13. OTX referenced the domain in two pulses on the same date. The PhishDestroy internal listing included bencrest.shop as of 2026-10-13. A PageSpeed performance score of 75 was recorded on 2026-10-13.
Interpretation
The VirusTotal record contains scan-based measurements for bencrest.shop, showing how multiple security engines evaluated the domain. OTX provides intelligence context with its pulse references, which are curated entries. PhishDestroy documents the domain in its internal listing, offering a catalogue entry for further review. These sources together describe the domain’s technical and security profile as recorded on their respective dates.
Recommended Actions
For bencrest.shop, preserve the VirusTotal scan results and OTX pulse references for comparison with future records. Retain the PhishDestroy internal listing entry to monitor any changes in its catalogue status. Review the PageSpeed performance score alongside other technical metrics for a comprehensive assessment.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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: 9 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
Netcraft
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of bencrest.shop· checked Oct 13, 2026
75
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
5.1s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
78ms
Total Blocking Time
SI
3.43s
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 05:49:37 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 195.96.130.209.
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
bencrest.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.
4 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 · bencrest.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.
