탐지를 보고하는 보안 엔진: 11. 일치를 보고하는 공개 차단 목록: 2. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is complaint@gname.com.
The latest stored availability evidence still shows the domain reachable; 2 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Elapsed since first report
2 months
Reports sent
1
Latest case ID
PD-20260804-8C56C5
Current status
HTTP 200 at latest stored check
보고서 요약
catfee.energy — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Binance; 사기 유형: Crypto Drainer. 증거 요약: VirusTotal 11/89 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. 등록기관: GNAME.COM.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
Analysis of the domain catfee.energy, observed on August 04 2026, shows limited public intelligence but several indicators of compromise. The domain was submitted to VirusTotal where 91 scanning engines examined the site; none reported a detection at the time of analysis. While a clean result might suggest an absence of known malware signatures, the lack of detections does not constitute evidence of legitimacy, especially given the domain’s appearance on a security blocklist. The blocklist entry is corroborated by PhishDestroy, which has actively blocked catfee.energy and classified it as a phishing resource.
No additional data such as registrar details, hosting IP, SSL certificate information, HTTP response codes, or page‑title metadata are currently available in the intelligence feed. Consequently, the infrastructure behind the domain remains opaque, and the specific brand or service being spoofed cannot be identified from the existing artifacts. Defenders should treat catfee.energy as a high‑confidence malicious indicator. Immediate mitigation steps include adding the domain to outbound and inbound deny lists across firewalls, proxy servers, and DNS filtering solutions.
Security information and event management (SIEM) rules should be updated to flag any DNS queries, HTTP requests, or email links containing the domain. Continuous monitoring of threat‑intel feeds for new indicators—such as IP address associations, SSL certificate changes, or emerging blocklist entries—will help refine detection capability. Because the domain has already been flagged by PhishDestroy, organizations employing that service will benefit from automatic blocking, but independent controls remain advisable. Until further forensic evidence is gathered, the recommendation is to maintain a strict deny‑list posture for catfee.energy and to educate end‑users about unsolicited communications that might reference the domain.
Extracted from stored page analysis
Observed indicators
3 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
등록 정보생성됨 2026년 7월 17일 (86d · New)—Expires 2027년 7월 17일
HTTP 상태200
기술 세부 정보Provenance & timestamps
최초 발견2026년 8월 4일
DOM Analysisanalyzed 2026년 10월 9일score 100/1009 brand signals
IoC Extractionscanned 2026년 8월 4일3 wallet · 0 Telegram IoCs
Submitted URLhttps://catfee.energy/
Favicon Hash
사건 ID
ICANN OVERSIGHT
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:30:39 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:30:39 UTClast content: 2026-10-11 10:30:39 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.
기술 · 1 identified
D
DDoS-Guard
보안
DDoS-Guard is a Russian Internet infrastructure company which provides DDoS protection, content delivery network services, and web hosting services.
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-08-04 03:17:08 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 186.2.175.25.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 웨이백 머신 — historical evidence archived
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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.
