PhishDestroy first observed bearfootstudio.shop on Oct 11, 2026. Current evidence score: 73/100 (critical).
AlienVault OTX listed 4 community pulse references (not vendor detections) on Oct 11, 2026 at 16:10 UTC. URLScan captured the page on Oct 11, 2026 at 14:22 UTC.
The collector marked the hostname reachable on Oct 11, 2026 at 14:22 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 11, 2026 at 12:22 UTC. At collection time, the hostname resolved to 23.252.79.185 on AS199242 (Malakmadze Web LLC). The recorded endpoint location is GE. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt / YE2 as the certificate issuer with validity through Jan 1, 2027; checked Oct 11, 2026 at 16:02 UTC.
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:22:15 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 14:22:15 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:22:15 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.185.
脅威対応 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.
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.
