bearfootstudio.shop was observed on 2026-10-11, with a PhishDestroy internal listing recorded on that date. The domain was also referenced in four OTX pulses, providing additional context for its security profile.
Recorded Evidence
On 2026-10-11, bearfootstudio.shop was listed in the PhishDestroy internal catalogue. OTX referenced the domain in four separate pulses on the same date. The domain's SSL certificate was issued by Let's Encrypt / YE2 and scanned on 2026-10-11.
Interpretation
The PhishDestroy listing documents a publisher-owned catalogue entry for bearfootstudio.shop, which is a type of internal measurement. OTX pulses provide external threat intelligence references, offering a broader scope of observation. The evidence covers multiple aspects of the domain's recorded presence, allowing for comparison across different types of security records.
Recommended Actions
For bearfootstudio.shop, preserve the PhishDestroy internal listing and OTX pulse references as primary records for ongoing review. Compare future evidence to these documented entries to track any changes or new observations. Maintain a record of the SSL certificate scan as part of technical monitoring efforts.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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
6 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.
