탐지를 보고하는 보안 엔진: 4. 일치를 보고하는 공개 차단 목록: 1. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
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; 20 days 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.
judaohoue.cc is an impersonation phishing site whose pages carry the title JUDAO3, a name made to pass as a legitimate platform. Its audience is crypto users, and the domain also appears on ScamSniffer, a blocklist focused on web3 fraud. PhishDestroy first flagged it on 2026-09-29. As of 2026-10-19 the site was still online and serving its content, so it remains a live risk.
How the scam works
Impersonation pages copy the look and wording of a trusted service so that visitors believe they are on the real one. Under the JUDAO3 branding, the site invites users to log in, register, deposit or connect a wallet. Anything typed or approved there goes to the operators. That can mean account credentials and one-time codes, money sent as "deposits", or permissions that let them move tokens out of a connected wallet.
Evidence
On 2026-10-10, 4 of 92 VirusTotal engines marked the domain as malicious: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a small share, and it means many browsers and security tools may still load the page without any warning. Two blocklists back the classification, PhishDestroy and ScamSniffer. The domain is also referenced in 4 AlienVault OTX threat pulses, which shows that other researchers are tracking it.
Infrastructure
The domain was registered on 2026-09-21 through Gname.com Pte. Ltd. PhishDestroy flagged it eight days later, a short gap that fits a site built for a quick campaign. Traffic passes through Cloudflare, Inc. (IP 188.114.97.3, located in Canada), so the server actually hosting the content is not visible from the outside. The site uses a free Let's Encrypt certificate, which means the padlock in the browser says nothing about whether the site is legitimate.
What to do
Do not log in, deposit or connect anything on judaohoue.cc. If you entered a password, change it right away on the genuine service and on any other account that used the same password, then turn on app-based 2FA. If you connected a wallet or signed a transaction there, revoke the approvals you granted to unfamiliar contracts with a token-approval checker, and move remaining funds to a fresh wallet. Report any losses to your exchange and to the police. Defenders should block the domain at DNS and proxy level and watch logs for earlier visits by users.
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-19 10:29:56 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-19 10:29:56 UTClast content: 2026-10-19 10:29:56 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.
기술 · 4 identified
H
HSTS
보안
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
지금 당장 어떻게 해야 할까요?
긴급
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 judaohoue.cc)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(CN)
