URLQuery
2 det.
报告degenhook.com — 未验证. 证据摘要: URLQuery 2 det.; URLScan capture; 1 external blocklist match (ScamSniffer); PhishDestroy score 58/100. 注册商: Name.com.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
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.
针对该主机的爬虫与浏览器观察记录,以及针对“Keitaro”式流量分配系统的实时指纹检测。
ns1cny.name.comns2ckr.name.comns3jkl.name.comns4hny.name.comLocation describes the IP network.
c625af8ec7fe64ae55cbf8c266c449bfcd896f8adf4acb1b6b7deb1b52e85027Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
34.111.179.208. 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20261011-B39B7D Recipient: abuse@name.com AUP & Terms of Service Violations: Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices. Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension. Applicable Legal Framework (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent