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 malicious…
为保留原始取证记录,下方的 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
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.