On 2026-10-13, benkstech.shop was observed as listed in the PhishDestroy internal database, according to a recorded source observation. Multiple security intelligence sources provide technical records for benkstech.shop, supporting a review of its network profile and detection history.
Recorded Evidence
VirusTotal documented 5 detections out of 92 scanners for benkstech.shop on 2026-10-11. OTX referenced the domain in 2 pulses as of 2026-10-13. The PhishDestroy internal listing included benkstech.shop on 2026-10-13. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-13. PageSpeed measured a performance score of 77 for the domain on 2026-10-13.
Interpretation
PhishDestroy contains an internal listing for benkstech.shop, recording its presence in the publisher's catalogue. VirusTotal provides a quantitative measurement of detections from its scanner network, while OTX documents the domain's inclusion in intelligence pulses. These records offer a technical snapshot across different security sources and allow for comparison of evidence types.
Recommended Actions
For benkstech.shop, preserve the VirusTotal detection record and OTX pulse references for ongoing monitoring. Retain the PhishDestroy internal listing to maintain context for future assessments. These source records can be used to compare and track changes in the domain's technical and security profile.
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 06:27:05 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 06:27:05 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 benkstech.shop· checked Oct 13, 2026
77
Needs Work
Performance
FCP
2.92s
First Contentful Paint
LCP
4.22s
Largest Contentful Paint
CLS
0.013
Cumulative Layout Shift
TBT
192ms
Total Blocking Time
SI
3.52s
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 06:27:05 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 31.222.234.229.
威胁响应 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.
