VirusTotal
0 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: 3-argos-it.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 0/89; PhishDestroy score 68/100. レジストラ: Cloudflare Pages.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
0 / 89 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
3-argos-it.pages.dev is an impersonation phishing page that copied Cloudflare's branding. It targeted people who recognise and trust Cloudflare's name. These include site owners with Cloudflare accounts and ordinary visitors used to passing Cloudflare security screens. PhishDestroy first flagged it on 2026-08-05. The site has been offline since 2026-09-13, its content is blocked by the hosting provider, and it was still dead when last checked on 2026-10-19.
Cloudflare look-alikes usually take one of two forms. The first is a fake account sign-in that captures the login for a Cloudflare dashboard, which controls a victim's domains and DNS. The second is a counterfeit 'verify you are human' screen that tricks visitors into handing over data or running something on their device. Losing a Cloudflare login can mean losing control of every website and domain attached to that account. The page title now reads 'Suspected Phishing | Cloudflare', which is Cloudflare's own warning interstitial, while our classification of the original content is Cloudflare impersonation.
Independent support is thin. VirusTotal returned 0 detections out of 89 engines on 2026-09-13, the same day the site went offline. PhishDestroy is the only blocklist carrying this domain. The zero score does not make the page safe. Short-lived pages on free hosting often disappear before scanning engines catch up, and the provider's own phishing block on the content is a stronger signal than the empty scan.
The subdomain was created on 2026-07-29, just seven days before PhishDestroy detected it. That quick turnaround is typical of disposable phishing pages. It sat on Cloudflare Pages, a free static-hosting service, and resolved to Cloudflare, Inc. network space geolocated to Canada. The page therefore impersonated Cloudflare while running on Cloudflare's own platform, which is how the provider was able to pull it. Its certificate from Google Trust Services was issued automatically, so the padlock said nothing about whether the page was legitimate.
If you entered Cloudflare credentials on this page, change your Cloudflare password at once and enable or reset two-factor authentication. Then revoke any API tokens and review your account for new members, DNS changes or altered redirects. If you followed on-screen 'verification' instructions that asked you to copy, paste or run anything, scan the device and change passwords stored in its browser. Defenders should block the domain and alert on Cloudflare-branded login or verification pages served from free pages.dev subdomains. They should also remind staff that real Cloudflare sign-ins never live on such addresses.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
646b63dad6e866252cec8d4c5666c6c0433167a5353eb53044e4adba58468ee0Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
不明→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
到達可能→利用不可
No threat flag
View source0/89 engine detections
View source3-argos-it.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:1 件
カテゴリPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-08-01T06:29:07.659Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
3-argos-it.pages.dev
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 ↗
3-argos-it.pages.dev)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.