The domain bencco.shop was observed in a PhishDestroy internal listing on 2026-10-13, which provides a dated entry for its inclusion in the publisher catalogue. VirusTotal also recorded a scan for bencco.shop, offering a technical snapshot from 2026-10-07.
Recorded Evidence
VirusTotal checked bencco.shop on 2026-10-07, recording 0 detections out of 92 scanners. The domain was registered with DYNADOT LLC on 2026-07-26. PhishDestroy documented an internal listing entry for bencco.shop on 2026-10-13. The domain was first observed on 2026-10-13, establishing a timeline for its recorded activity.
Interpretation
PhishDestroy contains a dated listing entry for bencco.shop, which documents its presence in a publisher catalogue. VirusTotal provides a technical measurement of detections, capturing the domain's status across multiple scanners at a specific point in time. The evidence allows for comparison between registration, catalogue inclusion, and external scanning records without combining their metrics.
Recommended Actions
For bencco.shop, retain the PhishDestroy internal listing entry and VirusTotal scan results as reference points for ongoing assessment. Use these records to compare future observations and catalogue entries, ensuring all evaluations are based on documented evidence from named sources.
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.
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.
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:41 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 212.52.28.20.
威胁响应 Pipeline
发现
Analysis
Monitoring
5 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.
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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)
