The domain benvibe.shop was recorded in the PhishDestroy internal listing on 2026-10-13, with a PageSpeed performance score measured at 75 on the same date. OTX also referenced the domain with three pulses, providing additional context for its security profile.
Recorded Evidence
PhishDestroy documented an internal listing for benvibe.shop on 2026-10-13. VirusTotal checked the domain on 2026-10-11, recording 9 detections out of 92 total scanners. OTX referenced the domain in three pulses as of 2026-10-13. The PageSpeed performance score was measured at 75 on 2026-10-13.
Interpretation
The PhishDestroy internal listing contains a record of benvibe.shop, documenting its inclusion in a publisher-managed security catalogue. VirusTotal provides a technical measurement by recording how many security scanners detected the domain. OTX adds further context by referencing the domain in multiple intelligence pulses. These sources together describe a range of recorded security and performance observations for benvibe.shop.
Recommended Actions
Preserve the PhishDestroy internal listing and VirusTotal detection records for benvibe.shop as reference points for future analysis. Compare OTX pulse counts and PageSpeed performance scores over time to track changes in external intelligence and technical metrics. Continue collecting dated records from these sources to maintain an updated evidence profile for benvibe.shop.
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.
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:18:01 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 06:18:01 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 benvibe.shop· checked Oct 13, 2026
75
Needs Work
Performance
FCP
2.88s
First Contentful Paint
LCP
4.53s
Largest Contentful Paint
CLS
0.007
Cumulative Layout Shift
TBT
194ms
Total Blocking Time
SI
3.93s
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:18:01 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 37.72.142.130.
威胁响应 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.
(US)
