beerenbergdirect.shop returned an HTTP status 200 on 2026-10-12, documenting a successful response at that time. The domain was also listed in the publisher's PhishDestroy catalogue on the same date.
Recorded Evidence
On 2026-10-12, the HTTP status for beerenbergdirect.shop was recorded as 200. The domain appeared in the PhishDestroy internal listing as of 2026-10-12. VirusTotal checked the domain on 2026-10-11, recording 4 detections out of 92 total scanners. OTX pulses were observed on 2026-10-12. The registrar was Dynadot Inc., and the SSL certificate was issued by Let's Encrypt / YE1.
Interpretation
The PhishDestroy listing documents the domain's inclusion in an internal catalogue, which is a publisher-maintained record. VirusTotal provides a measurement of detections from multiple scanners, offering a view into how external security vendors have evaluated the domain. The OTX pulses record further external intelligence activity, adding context to the available evidence. These sources together provide a snapshot of how beerenbergdirect.shop was observed within security monitoring systems on the referenced dates.
Recommended Actions
For beerenbergdirect.shop, retain the HTTP status, PhishDestroy listing, and VirusTotal detection records for ongoing comparison. Review OTX pulse entries for additional context in future assessments. Use these dated records to track any changes in the domain's security profile over time.
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.
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.
技术 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Gridinsoft
Netcraft
网站性能分析
Google PageSpeed Insights — mobile performance audit of beerenbergdirect.shop· checked Oct 12, 2026
66
Needs Work
Performance
FCP
3.04s
First Contentful Paint
LCP
9.16s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
136ms
Total Blocking Time
SI
4.62s
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-12 09:03:50 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 195.96.131.13.
威胁响应 Pipeline
发现
Analysis
Monitoring
8 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)
