ijdkc.com — 콘텐츠를 사용할 수 없음. 브랜드 사칭: Cloudflare; 사기 유형: Impersonation. 증거 요약: VirusTotal 8/89 (alphaMountain.ai, BitDefender, CRDF, G-Data, Gridinsoft); Google Safe Browsing flagged; PhishDestroy score 100/100. 등록기관: Cloudflare.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
ijdkc.com is a phishing domain that impersonated Cloudflare and was aimed at people who use or trust the company's services, especially website operators with Cloudflare accounts. PhishDestroy first flagged it on 2026-09-06. The site went offline on 2026-09-15, and as of 2026-10-19 its DNS no longer resolves. It is dead, but it remains on our blocklist in case it is revived or reused.
How the scam works
Cloudflare impersonation pages usually copy the look of the Cloudflare dashboard login or its browser check screen. The fake page then asks the visitor for their email, password or a verification step. Anyone who enters credentials gives attackers control of a Cloudflare account, which can mean control of DNS, traffic routing and the websites behind it. The page title read "Suspected Phishing | Cloudflare", which matches the wording of Cloudflare's own phishing warning screen, while PhishDestroy classifies the domain itself as an impersonation phishing page.
Evidence
Eight of 89 VirusTotal engines flagged the domain as of 2026-09-17: alphaMountain.ai, BitDefender, CRDF, G-Data, Gridinsoft, Kaspersky, PhishFort and SOCRadar. That is a modest count, but it comes from a mix of general antivirus vendors and specialists in brand abuse and threat intelligence, so they reached the same verdict independently. Google Safe Browsing labels the site as social engineering, which triggers warnings in major browsers. The domain also appears in four AlienVault OTX threat pulses alongside the PhishDestroy listing.
Infrastructure
The domain was registered on 2026-08-31, only six days before PhishDestroy caught it, and it stopped serving content nine days after that. A domain that is registered, used briefly and abandoned like this fits a disposable phishing campaign. It was registered through Cloudflare, Inc. and hosted on Cloudflare's network with a Canadian IP, so the operator used the impersonated brand's own infrastructure. Its certificate came from Google Trust Services, the standard issuer for sites behind Cloudflare, and says nothing about who ran the page.
What to do
If you typed Cloudflare credentials into this site, change your Cloudflare password immediately and sign out all active sessions. Turn on app-based or hardware-key two-factor authentication. Review your account for unfamiliar API tokens, team members, DNS changes or new page rules, and reverse anything you did not make. If you reused that password anywhere else, change it there too. Security teams should block the domain, search proxy and email logs for visits between 2026-08-31 and 2026-09-15, and reset credentials for any user who reached it.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-19 01:14:31 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-15 22:17:59 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:59 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:27 UTC · precision low · basis bounded
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.
기술 · 2 identified
Cloudflare
CDN
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 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 ijdkc.com)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.
(US)
