VirusTotal
7 / 89 engine detections
보고서 열기“Suspected Phishing | Cloudflare”
52pv-2ujnn0q3r9-t5p6.com — 연결 가능 · 액세스가 제한됨 (HTTP 403). 브랜드 사칭: Cloudflare; 사기 유형: Impersonation. 증거 요약: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, PhishFort); Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 90/100. 등록기관: GoDaddy.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
7 / 89 engine detections
보고서 열기악성
보고서 열기DBL_PHISH
4 community references
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
52pv-2ujnn0q3r9-t5p6.com is an impersonation phishing page that used Cloudflare's brand. Its targets are people who manage websites, domains and DNS through Cloudflare. PhishDestroy first flagged it on 2026-08-10. The site has been offline since 2026-09-13, its content is blocked by the provider, and it was still dead at the last check on 2026-10-19. The current page title, "Suspected Phishing | Cloudflare", matches Cloudflare's own warning screen, while our classification covers the impersonation content the domain served before the block.
Cloudflare impersonation lures usually arrive as urgent notices about a domain, DNS, SSL or a security check. They push the visitor to a lookalike sign-in page. Anything typed there, including email, password and sometimes a one-time code, goes straight to the operator. A hijacked Cloudflare account is valuable. It lets an attacker reroute DNS, redirect a company's traffic, issue API tokens or take over the domains behind it, so the loss can reach well beyond one password.
Seven of 89 VirusTotal engines flagged the domain as of 2026-09-13: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, PhishFort, SOCRadar and Webroot. That count is modest, but it includes a brand-protection specialist and several commercial web filters. Spamhaus lists the domain in its DBL under the phishing category, which affects mail and DNS filtering widely. Four AlienVault OTX threat pulses also reference it, and it is on the PhishDestroy blocklist.
The randomized, meaningless domain name is typical of throwaway phishing hosts that are registered in bulk and discarded after takedown. It was registered through GoDaddy.com, LLC and resolved to Cloudflare, Inc. network space at 104.18.27.248, geolocated to Canada. Its TLS certificate came from Google Trust Services (WE1), which is what Cloudflare's edge normally serves. The padlock on this site therefore said nothing about whether it was legitimate. Being proxied through Cloudflare likely made the provider-side block straightforward once the abuse was confirmed.
If you entered credentials on this domain, change your Cloudflare password immediately and sign out all active sessions. Reset or re-enroll two-factor authentication, and revoke any API tokens or keys you do not recognize. Check your DNS records, page rules, member list and audit log for changes you did not make. Do the same for any other service that shares that password. Defenders should block the domain at mail and web gateways and search inbound mail for Cloudflare-themed lures pointing to random-string domains. They should also remind staff that real Cloudflare sign-ins only happen on Cloudflare's own dashboard.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
yoxall.ns.cloudflare.comLocation describes the IP network.
9303c92fc482b743ffa6e32d6c53ea91c12aa871e0825c02b78c6f2cfc5e3f86Saved 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
52pv-2ujnn0q3r9-t5p6.com
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
이용 불가→접속 가능
0→7
접속 가능→이용 불가
4 community references
View sourceNo threat flag
View source7/89 engine detections
View source52pv-2ujnn0q3r9-t5p6.com
View source저장된 유사 도메인 142개
전체 142개 중 100개 표시
커뮤니티 신고 2건
범주IMPERSONATION
Brand abuse: impersonation, fake affiliation, impersonating Las Vegas Sands Corp
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 ↗
52pv-2ujnn0q3r9-t5p6.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.