Skip to security report
Analytics Dashboard
Domain security report
prozones.cc favicon

prozones.cc

“Prozone Login: Prozone cc | Prozone.cc Store Login”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 4/89 Scam type: Credential Phishing
OTX: 24 refs Mar 3, 2026 1 Report Sent CDN
API
Registrar
Key-Systems
Resolved IP
172.67.201.16
Registered
Mar 3, 2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@key-systems.net. The latest stored availability evidence still shows the domain reachable; 7 months 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.

Elapsed since first report
7 months
Reports sent
1
Latest case ID
PD-20260303-611805
Current status
HTTP 301 at latest stored check

Additional indicators at a glance

VirusTotal
VirusTotal
4 det.
OTX references
24 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates
WE1 · Hostname coverage not recorded
Age
8 mo
Observed status
Last known active 301
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

10 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

4 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

checked — no detections recorded

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

PhishStats

checked — no match recorded

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

24 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

DNS blocks

14 checked — no blocks

Observation time not recorded
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
4/89
OTX
24 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

The domain prozones.cc was registered on March 03, 2026 through a German registrar and is presently active with a high‑risk rating. The site presents a login interface titled “Prozone Login: Prozone cc | Prozone.cc Store Login,” a classic lure designed to harvest user credentials. HTTP requests return a 200 status, indicating the page is fully operational.

Infrastructure analysis shows the domain resolves to IP address 172.67.201.16, which belongs to an autonomous system operated by a major content delivery network located in the United States. Authoritative nameservers archer.ns.cloudflare.com and opal.ns.cloudflare.com resolve the domain, and the TLS certificate is issued by a widely trusted certificate authority (Google Trust Services) under the WE1 profile, providing a valid HTTPS connection. Fingerprinting tools detect a modern web stack comprising Node.js, Vue.js, Nuxt.js, and support for HTTP/3, suggesting the site is built with contemporary development frameworks.

Threat intelligence sources corroborate malicious intent: a single security vendor on VirusTotal flagged the domain, and the site appears on one public blocklist. PhishDestroy has explicitly blocked the domain, and the Gridinsoft trust score is 0 out of 100, indicating a lack of reputation. The observed characteristics align with credential phishing campaigns that impersonate legitimate brand login portals to capture user names and passwords.

While the current evidence confirms the domain’s use for credential harvesting, the limited number of VirusTotal detections leaves open the possibility of additional undisclosed malicious activity. Defenders should block DNS resolution for prozones.cc, deny outbound connections to its IP address, and enforce multi‑factor authentication for accounts that may be targeted. Continuous monitoring of the IP range and associated certificate details is recommended to detect any future repurposing of the infrastructure.

Data coverage & collection

24 · datasets with records / 7 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
4 / 89 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source record
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
24 · community references
External blocklists
0 · external matches
PhishStats
Dated lookup retained
Cloudflare Radar
cleanCollection time not recorded
DNS security filters
0 / 14 · provider blocksCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Key-Systems GmbHCollection time not recorded
Network & DNS
172.67.201.16 · 1 · nameserversCollection time not recorded
TLS certificate
WE1
Page captures
3 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
99/100 · mobile performance
Response records
1 · outgoing report records
Availability history
30 · stored state changes
Source observation history
5 · stored source events
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 7

These checks have no retained result. This does not mean they passed or that a scan is running.

  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Lookalike relationships
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Key-Systems GmbH · 172.67.201.16 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-03activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Key-Systems DE(DE)
Abuse contactabuse@key-systems.net, abusereport@key-systems.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for prozones.cc →
RegistrationCreated Mar 3, 2026 (227d) — Expires Jan 10, 2028
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedMar 3, 2026
DOM Analysisanalyzed Jul 9, 2026score 81/100
Submitted URLhttp://prozones.cc/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.201.16
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1
  • opal.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-03-12 09:57:35
Valid until
2026-06-10 10:55:23
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-03-15 05:40:31 UTC
Collection source
PhishDestroy collector
Certificate fingerprintad0696c315cc6a544ee4263deabc6c1b5c6f01dd023b72cd99f8ec3ea3b23673

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 172.67.201.16rapiddns.io

Latest Classified Outcome 2026-10-17 02:07:31 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-17 02:07:31 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 02:07:31 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 5 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of prozones.cc · checked Mar 3, 2026

99
Good
Performance
FCP
1.2s
First Contentful Paint
LCP
2.03s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.27s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

Not observed No cloaking was observed in the stored scan

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Server header seen by scanner
cloudflare

Scanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://prozonecc.com/; server=cloudflare

Title shown to the security scanner301 Moved Permanently
Title shown to a browser visitorProzone Login: Prozone cc | Prozone.cc Store Login
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Unreachable

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-08-06 22:15:01 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  2. Domain Status Transition 2026-08-06 10:26:30 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  3. VirusTotal Detections Update 2026-03-05 02:00:54 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
  4. Cloudflare Radar Scan 2026-03-03 20:20:06 UTC
    Source: Cloudflare Radar
    Event details
    Cloudflare Radar scan registered: View Radar report.
  5. VirusTotal Detections Update 2026-03-03 20:15:05 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: Forcepoint ThreatSeeker.
Stored observation history35

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 30
  1. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  17. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    redirected→Unknown

    stale_current_evidence

  19. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  20. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  21. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  23. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  25. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  26. Availability monitor · Recorded state

    Unavailable→Reachable

  27. Availability monitor · Recorded state

    Reachable→Unavailable

  28. VirusTotal · Detection count

    1→2

  29. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/cd311ae3-8377-4824-939b-fe92c35e8b5e

  30. VirusTotal · Detection count

    0→1

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
prozones.cc detected and queued for full analysis
Mar 3, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Mar 24, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Mar 14, 2026
VirusTotal
4/89 recorded on VirusTotal
Sep 13, 2026
OTX Community References
24 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Sep 29, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Mar 24, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Aug 7, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 500); the cause was not independently established.
Aug 6, 2026
VT Detection +1
+1 new detection (1 → 2): SOCRadar
Mar 5, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 3, 2026
VT Detection +1
+1 new detection (0 → 1): Forcepoint ThreatSeeker
Mar 3, 2026
Initial Abuse Report (#1)
Sent to 3 abuse contacts at Key-Systems GmbH with forensic evidence
abuse@key-systems.netabuse@verisign-grs.comcompliance@icann.org
Mar 25, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Mar 3, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen Mar 3, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 4 det. ChainPatrol URLQuery Report stored SSL Labs Hostname coverage not recorded CF Radar Open report OTX 24 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260303-611805 Recipient: abuse@key-systems.net
Page title stored with report: Prozone Login: Prozone cc | Prozone.cc Store Login
PDF notice generated Notice text archived (569 chars)
Abuse notice text as sent to the provider 
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (CA):
Criminal Code Section 342.1
Criminal Code Section 380 - Fraud
PIPEDA
Canadian law prohibits computer fraud and unauthorized access.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including prozones.cc)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: prozones.cc

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Prozone Login: Prozone cc | Prozone.cc Store Login”.

VirusTotal detections for prozones.cc: 4 (2026-09-13 02:08:15 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/prozones.cc"
  title="PhishDestroy threat report for prozones.cc"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>