VirusTotal
4 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: djknmmk.com — コンテンツが利用できません. 証拠の概要: VirusTotal 4/89 (alphaMountain.ai, CRDF, Gridinsoft, SOCRadar); Google Safe Browsing flagged; CF Radar…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 89 engine detections
レポートを開く悪意あり
レポートを開くThreat flag recorded
レポートを開く4 community references
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
djknmmk.com is a phishing domain that impersonated Cloudflare, aiming at people who trust that brand, such as site owners with Cloudflare accounts and visitors who see Cloudflare pages every day. PhishDestroy first flagged it on 2026-09-06, two days after registration. The site has been offline since 2026-09-15, and on our last check, on 2026-10-19, its DNS was no longer resolving.
The page carried the title "Suspected Phishing | Cloudflare", which matches the wording of Cloudflare's own phishing warning interstitial rather than a typical login lure. We still classify the domain as Cloudflare impersonation phishing. Schemes like this borrow a familiar Cloudflare look, such as a security check, a warning or an account prompt, so the victim lowers their guard and follows instructions. That usually ends with credentials typed into an attacker-controlled form or a malicious next step. A stolen Cloudflare login can give an attacker control over a victim's domains, DNS and the traffic of every site behind them.
Four of 89 VirusTotal engines flagged the domain in a 2026-09-17 check: alphaMountain.ai, CRDF, Gridinsoft and SOCRadar. That is a low count, but Google Safe Browsing independently lists it under SOCIAL_ENGINEERING, the category used for deceptive phishing pages. The domain also appears in four AlienVault OTX threat pulses, which shows other researchers tracked it separately. It is on the PhishDestroy blocklist.
The domain was registered on 2026-09-04 and was already serving its phishing page when we caught it two days later. It was short-lived and disposable, offline within about eleven days. It was registered through Cloudflare, Inc. and hosted on Cloudflare's network, with the serving IP located in Canada. The operator placed a Cloudflare impersonation on Cloudflare's own infrastructure, which can make the page look more convincing to anyone checking where it is hosted.
If you entered a Cloudflare login on this site, change that password immediately, along with the password for any account that reused it. Turn on or reset two-factor authentication, revoke any API tokens you don't recognize, and review your account's audit log for unfamiliar DNS, SSL or member changes. If you downloaded or ran anything the page offered, scan that device before using it again. Defenders should block djknmmk.com, search proxy and DNS logs for visits between 2026-09-04 and 2026-09-15, and warn users that genuine Cloudflare warnings never ask for credentials.
Edge-IP の評判はこのドメインに起因しません。
matt.ns.cloudflare.comLocation describes the IP network.
0ec074acd785df321c019c04e40de01889f28460e8443778ee9e38c38155c565djknmmk.com*.djknmmk.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of djknmmk.com · checked Sep 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
利用不可→到達可能
到達可能→利用不可
No flag recorded→Flag recorded
到達可能
4 community references
View sourceThreat flag recorded
View source4/89 engine detections
View sourcedjknmmk.com
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as other. Threat detected at 2026-09-06T13:02:52.679Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
djknmmk.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
djknmmk.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.