VirusTotal
12 / 89 engine detections
보고서 열기“Suspected Phishing | Cloudflare”
Cloudflare 사칭: 23c32c.pages.dev — 연결 가능 · 액세스가 제한됨 (HTTP 403). 증거 요약: VirusTotal 12/89 (Criminal IP, alphaMountain.ai, BitDefender, ESET, Forcepoint…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
12 / 89 engine detections
보고서 열기악성
보고서 열기Threat flag recorded
보고서 열기no community references
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
23c32c.pages.dev is an impersonation phishing page that posed as Cloudflare, aimed at people who trust the brand's login screens and security prompts, especially website owners and administrators. It sat on a free Cloudflare Pages subdomain, so the address itself carried a Cloudflare-related name. PhishDestroy first detected it on 2026-08-12. The site has been offline since 2026-09-13, and the provider is now blocking its content, which was still the case on 2026-10-19.
Cloudflare impersonation pages usually copy the look of a Cloudflare sign-in or a "verify you are human" check. They push the visitor to type in account credentials or follow instructions that hand control to the attacker. A stolen Cloudflare account can be costly because it controls DNS, domains and security settings, so an attacker can redirect a victim's websites or intercept their traffic. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning wording rather than the original lure, while we classify the site as Cloudflare impersonation.
Twelve of 89 VirusTotal engines flagged the domain as of 2026-09-14. The flagging vendors include BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, Criminal IP and Google Safe Browsing. Google Safe Browsing separately classifies it as SOCIAL_ENGINEERING, the category browsers use for deceptive pages that harvest credentials. PhishDestroy lists it on its blocklist. Taken together with the provider-side block, several independent parties reached the same conclusion.
The subdomain was created on 2026-08-10 and detected two days later, which suggests a short-lived, throwaway deployment. It ran on Cloudflare Pages behind Cloudflare, Inc. network space geolocated to Canada. Using Cloudflare's own free hosting to imitate Cloudflare gave the page a believable address and a valid certificate from Google Trust Services. That padlock shows the connection was encrypted, not that the site was legitimate.
If you entered Cloudflare credentials on this page, change your password right away and enable or reset two-factor authentication. Then end all active sessions in the dashboard. Rotate API tokens and global API keys, and check your DNS records, page rules, workers and account members for changes you did not make. Only sign in to Cloudflare by typing the official address yourself, never through a link or prompt from an unfamiliar subdomain. Defenders should block this hostname and watch for Cloudflare-branded lures served from free hosting subdomains.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
Location describes the IP network.
61e80235385e2a3f14469947e3dc1a0684936b98dba5da1e43fc8b7347727dd7Saved 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 flag recorded→Flag recorded
Threat flag recorded
View source12/89 engine detections
View source23c32c.pages.dev
View source저장된 유사 도메인 142개
전체 142개 중 100개 표시
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
23c32c.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 ↗
23c32c.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
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.