PhishDestroy first observed degenhook.com on Oct 11, 2026. Current evidence score: 58/100 (high).
Positive findings are stored from 2 sources: ScamSniffer and URLQuery. ScamSniffer listed the hostname in the separate external-blocklist snapshot on Oct 11, 2026 at 14:20 UTC. URLQuery recorded 2 detections; no observation timestamp was retained. Additional recorded evidence: URLScan captured the page on Oct 11, 2026 at 11:20 UTC.
The collector marked the hostname reachable on Oct 11, 2026 at 11:20 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 11, 2026 at 09:20 UTC. Registration records for the domain list Name.com, Inc. as the registrar and Jul 31, 2026 as the creation date. At collection time, the hostname resolved to 34.111.179.208 (AS396982 Google LLC). The recorded endpoint location is Kansas City, US. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt / YE1 as the certificate issuer with validity through Oct 29, 2026; checked Oct 11, 2026 at 13:02 UTC.
The record contains 2 positive source findings supporting the current phishing classification.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
IP 평판abuse score 18/10088 reportsFraud OrdersPhishingOpen ProxyEmail SpamPort ScanHackingSpoofingBad Web BotExploited HostWeb App Attackchecked 2026년 10월 11일
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 11:20:28 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 11:20:28 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 11:20:28 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 34.111.179.208.
위협 대응 Pipeline
발견
Analysis
Notifications
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.
보고서 
(US)
