VirusTotal
2 / 89
engines flag the domain
“Suspected Phishing | Cloudflare”
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; 1 month 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.
2 / 89
engines flag the domain
No threat flag
Not on Google threat lists at check time
No malicious flag
Browser scan with screenshot
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 172.67.128.17 · TLS: Google Trust Services
malicious
Each check shows its own collection time. Zero detections do not guarantee safety.
Cloudflareなりすまし: com-w.my — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 2/89 (CRDF, Forcepoint ThreatSeeker); URLQuery 1 alert; 2 external blocklist matches…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 89 engine detections
レポートを開く1 threat-system alert
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | com-w.my |
malicious | Sinkholed |
PhishDestroy threat report
com-w.my is a phishing domain that impersonates Cloudflare, the network and security provider behind a large share of websites and crypto front-ends. PhishDestroy first flagged it on 2026-09-18, only days after it appeared. The site went offline that same day, and when checked on 2026-10-19 it was still dead, with its content blocked by the hosting provider.
Cloudflare impersonation uses trust in the familiar security checks and account prompts that people pass through every day. Victims are shown a convincing copy of a Cloudflare screen or login and are asked to sign in or confirm an action. That can hand over account credentials and with them control of domains, DNS and the websites behind them. The domain's shape, starting with a fragment that resembles the end of a normal address, is a common trick to make a link look like it belongs to a legitimate site. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning text, while we classify the site as Cloudflare impersonation phishing.
Detection by antivirus-style scanners is thin. When checked on 2026-09-18, 2 of 89 VirusTotal engines (CRDF and Forcepoint ThreatSeeker) flagged it, so a clean result from most vendors offers no reassurance here. Stronger confirmation comes from the crypto-security community. The domain sits on the PhishDestroy, MetaMask and SEAL blocklists, which means wallet users relying on MetaMask's protections get a warning before the page loads.
The domain was registered on 2026-09-15 through Gname.com Pte. Ltd. and detected three days later, which fits a disposable domain built for a short campaign. It resolved to 188.114.96.3 on Cloudflare, Inc.'s network, geolocated to Canada. That makes this a Cloudflare lookalike running behind Cloudflare itself, and the provider ultimately blocked the content. Its Google Trust Services (WE1) certificate shows that the padlock in the browser says nothing about whether a site is legitimate.
If you entered a Cloudflare email and password on this site, change the password right away from Cloudflare's real dashboard and reset any other account that shares it. Enable or re-enroll two-factor authentication, sign out all active sessions, and rotate API tokens and keys. Review your audit log, DNS records, member list and page rules for changes you did not make. Defenders should block the domain at DNS and proxy level and search mail and chat logs for links to it. They should also warn staff that a real Cloudflare prompt never arrives on an unrelated domain.
Last checked
Edge-IP の評判はこのドメインに起因しません。
david.ns.cloudflare.comelinore.ns.cloudflare.comLocation describes the IP network.
760203a4e356db5de1f7f1e692bc71aca4a825f73c20e7de4096f777b868012cSaved 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 com-w.my · checked Sep 18, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
com-w.my
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
到達可能
PD-20260918-D49516
No threat flag
View source2/89 engine detections
View sourcePage captured
View sourcecom-w.my
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
PD-20260918-D49516 Recipient: complaint@gname.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
com-w.my)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.