bearcatwarehouse.shop was observed with a PhishDestroy internal listing on 2026-10-11, documenting its inclusion in a publisher-owned catalogue. The domain was also noted to have an SSL certificate issued by Let's Encrypt / YE1, recorded on the same date.
Recorded Evidence
PhishDestroy internally listed bearcatwarehouse.shop on 2026-10-11. OTX referenced the domain with four pulses as of 2026-10-11. The SSL certificate for bearcatwarehouse.shop was issued by Let's Encrypt / YE1 and scanned on 2026-10-11.
Interpretation
The PhishDestroy record contains a listing measurement, documenting bearcatwarehouse.shop's inclusion in its internal catalogue. OTX provides a pulse count, which is a form of community-driven intelligence referencing the domain. These sources offer a snapshot of the domain's status and recorded infrastructure on their respective dates.
Recommended Actions
For bearcatwarehouse.shop, preserve the PhishDestroy internal listing and OTX pulse records for ongoing comparison. Review future catalogue and intelligence entries to track any changes in the domain's referenced status.
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-11 14:18:27 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 14:18:27 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.
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-11 14:18:27 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.245.239.160.
威胁响应 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.
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.
