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.150.5 · TLS: Let's Encrypt
malicious
Each check shows its own collection time. Zero detections do not guarantee safety.
Cloudflareなりすまし: com-a.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-a.my |
malicious | Sinkholed |
PhishDestroy threat report
com-a.my is an impersonation phishing domain that borrows Cloudflare's name and branding to pass as part of the service millions of sites sit behind. Its presence on the MetaMask and SEAL blocklists shows it was relevant to crypto users. PhishDestroy first flagged it on 2026-09-18. The site has been offline since that same day and was still dead when last checked on 2026-10-19.
The domain name itself is a lure. A string like "com-a.my" is built to sit at the end of a longer address so a careless glance reads it as a familiar ".com" site. Cloudflare impersonation schemes usually show a fake "checking your browser" or verification screen. That screen then asks for a login, pushes a download, or tells the visitor to paste a command to "prove" they are human, which hands the attacker credentials or control of the device. The page title at last capture, "Suspected Phishing | Cloudflare," is Cloudflare's own warning interstitial rather than the lure itself, and we classify the domain as a Cloudflare impersonation.
Detection by antivirus-style scanners is thin. Only 2 of 89 VirusTotal engines, CRDF and Forcepoint ThreatSeeker, flagged it on 2026-09-18, so a clean-looking scan should not reassure anyone. The stronger signal comes from crypto-focused lists: MetaMask and SEAL both block it alongside PhishDestroy. The provider also placed its own phishing warning in front of the content.
The domain was registered on 2026-09-15 through Gname.com Pte. Ltd. and was caught three days later, a short lifespan typical of throwaway phishing domains. It resolved to Cloudflare, Inc. address space geolocated to Canada. That means a site impersonating Cloudflare was being served through Cloudflare's own network until the provider blocked the content. A free Let's Encrypt certificate gave it the padlock icon, which proves encryption, not legitimacy.
If you entered a password on this site, change it immediately wherever you reuse it, and turn on app-based or hardware two-factor authentication. If the page told you to download a file or paste a command into a terminal or the Run dialog, treat the device as compromised. Run a full malware scan and move any crypto from wallets on that machine to a new wallet created on a clean device. Defenders should block the domain, hunt in DNS and proxy logs for any lookup since 2026-09-15, and warn users that a genuine Cloudflare check never asks for credentials or commands.
Last checked
Edge-IP の評判はこのドメインに起因しません。
david.ns.cloudflare.comelinore.ns.cloudflare.comLocation describes the IP network.
cd76a02fc7ae55660a464c4843d47bcf2529c5d241be29696af5f4cdb171d7ceSaved 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-a.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-a.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-8AE5DA
No threat flag
View source2/89 engine detections
View sourcePage captured
View sourcecom-a.my
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
PD-20260918-8AE5DA 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-a.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.