VirusTotal
5 / 92 engine detections
Open reportprozone.st is a blocklisted domain detected by PhishDestroy on 2026-09-28. Risk: critical (88/100). Status: Last known active. Hosting: DDOS-GUARD LTD. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.
“Error 502”
5 / 92 engine detections
Open report3 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
prozone.st is classified by PhishDestroy as an impersonation phishing page. It poses as a service its visitors already trust so they hand over details they would only give the genuine site. PhishDestroy first flagged the domain on 2026-09-28. As of 2026-10-19 it was still online, sitting behind a protective proxy layer.
Impersonation pages copy the name, look and login flow of a known service. Victims usually arrive through search ads, social posts or direct messages. Whatever they type, whether usernames, passwords, one-time codes or recovery details, goes straight to the operators, who then take over the real account and anything of value in it. When we checked, the page title read "Error 502", a gateway error, while our classification is impersonation phishing.
Five of 92 VirusTotal engines flagged the domain as of 2026-10-10: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a small share of engines, but these five are independent threat-intelligence and URL-filtering sources that reached the same verdict. The domain also appears in three AlienVault OTX community pulses, so other researchers have tracked it as well. Among blocklists, it is currently listed by PhishDestroy only. Many browsers and security tools may therefore still let it load without a warning.
The site resolves to an address on the DDOS-GUARD LTD network in Russia. That provider's DDoS-protection front shields the server behind it and explains why the content is reachable only through a protection layer. The free, automated TLS certificate lets the page show a padlock in the browser, which says nothing about who runs it or whether it is legitimate.
If you entered a username or password on prozone.st, change that password now on the genuine service. Change it anywhere else you reused it too. Then turn on app-based or hardware-key two-factor authentication and sign out all active sessions. If you typed a one-time code or recovery phrase, treat the account as compromised. Check it for new devices, changed email addresses or unexpected transactions, and contact the real provider's support. Security teams should block the domain and the 185.178.208.187 address at DNS and proxy level. They should also search logs for earlier visits and warn users that the site may currently look like a harmless error page.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 019f3d1b-5bf4-76cc-9245-f4c5062e2ce4 |
|---|---|
| Final url | https://prozone.st/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://prozone.st/",
"from": "http://prozone.st/",
"status": 307
}
] |
| Ip | 185.178.208.187 |
| Ptr | ddos-guard.net |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.14.94",
"192.178.170.95",
"185.178.208.187"
] |
| Asns | [
"15169",
"57724"
] |
| Countries | [
"US",
"RU"
] |
| Document hash | 5a55d7d0be54da6e6c38500a4a316774a8eb93a34d58f3c7b6a32f11a3c27713 |
| Script hashes | [
"c2c6eb505a297d140db1e63b25fc62d848eec30233611a0f781da9f25eb401d7",
"fefa10ec9ee84784072b8c94ccee02d7725e03375e22a5843df66492988a16f2",
"dabfdd88060adb05f3c9e06de05c8b5e0811826cab3d1029a93d5ea4d99fd204",
"80918dec3954c68168b4ca0eac962819cc676670b5ef6ca5848ae908743a4d8e",
"e2e3f93693ed4bb51526913c8da03da5d44158892630d6438693c570a8a58240",
"d537a53bab8a5a2ef5e1ee4fd489ccf96d3c54e98f3e7b6cba354c99f9d506bc",
"984c0710e519b78cbcc8534a0c4edd8e61dab25e1bb0a65dc2fd17cea27c7a28",
"031f166ff95a9a41d840ed3b92617b89808badc9c6b617fa06921de02223e62f"
] |
| Globals | [
"noUiSlider",
"__NUXT__",
"webpackJsonp",
"installComponents",
"regeneratorRuntime",
"setImmediate",
"clearImmediate",
"onNuxtReadyCbs",
"onNuxtReady",
"_",
"Color",
"Chart",
"Pusher",
"$nuxt"
] |
| Cookies | [
"__ddg9_",
"__ddg1_",
"auth.strategy",
"auth.redirect",
"__ddg10_",
"__ddg8_"
] |
| Storage keys | [
"auth.strategy",
"auth.redirect",
"pusherTransportTLS"
] |
| Tls | {
"san": [
"prozone.st"
],
"cipher": "AES_128_GCM",
"issuer": "YR1",
"subject": "prozone.st",
"protocol": "TLS 1.3",
"valid_to": "2026-09-30T02:02:52Z",
"valid_from": "2026-07-02T02:02:53Z"
} |
| Domain age days | 5 |
| Apex age days | 5 |
| Tls age days | 5 |
| Tls valid days | 89 |
| Requests | 28 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "ddos-guard",
"content-type": "text/html; charset=utf-8",
"content-security-policy": "upgrade-insecure-requests;",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff"
} |
Observed: · Retrieved:
| Uuid | 3e96cab1-81fa-4018-ba9a-a1a194eb531b |
|---|---|
| Final url | https://prozone.st/ |
| Status | 502 |
| History | [
{
"url": "https://prozone.st/",
"status": 502
}
] |
| DOM structure hash | 8d29c88cc0ced0b2df474f2c28ccc6f5f38e8f8a14ae83ddaff694f7a06c7f02 |
| Document hash | 4231d489413c2f04116f74d2ecbd6552966cd89840ef5c56cd085d934cac4095 |
| Domain risks | [
"Login Screens",
"Miscellaneous"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "prozone.st",
"type": "A",
"value": "185.178.208.187"
}
] |
| Dnssec valid | false |
| Ip | 185.178.208.187 |
| Registration record | {
"registrar": "NordNIC",
"created": "2026-06-24T00:00:00Z",
"updated": "2026-06-24T00:00:00Z",
"expires": "2029-06-24T00:00:00Z",
"nameservers": [
"ns1.dnsserv.se",
"ns1.dnsserv.nu"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 52,
"malicious": 4,
"suspicious": 1,
"undetected": 35
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"SOCRadar": "suspicious",
"Gridinsoft": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Phishing (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "phishing and other frauds"
} |
| Registrar | NordNIC |
| Created | 2026-06-24T00:00:00Z |
| Updated | 2026-06-24T00:00:00Z |
| First seen | 2026-07-02T03:14:51Z |
| DNS records | [
{
"ttl": 3600,
"type": "NS",
"value": "ns1.dnsserv.nu"
},
{
"ttl": 7200,
"type": "SOA",
"rname": "registry.prq.se",
"value": "ns1.dnsserv.se"
},
{
"ttl": 3600,
"type": "A",
"value": "185.11.145.254"
},
{
"ttl": 3600,
"type": "A",
"value": "185.11.145.145"
},
{
"ttl": 3600,
"type": "NS",
"value": "ns1.dnsserv.se"
}
] |
| Dns at | 2026-10-10T02:00:37Z |
| Jarm | 28d28d28d00028d00042d42d000000e1ea2a807a629b496b664cf07ad7c08d |
| Certificate | {
"san": [
"prozone.st"
],
"issuer": "Let's Encrypt / YE1",
"serial": "68ba2df61cb4b733106c55c75ffc31f310a",
"sha256": "780f931e53f6e66896c665aed92b4035fbe599f324bec8405045144c41510b62",
"subject": "prozone.st",
"valid_to": "2027-01-06T19:58:52Z",
"valid_from": "2026-10-08T19:58:53Z"
} |
| Registration record | {
"registrar": "NordNIC",
"created": "2026-06-24T00:00:00Z",
"updated": "2026-06-24T00:00:00Z",
"nameservers": [
"ns1.dnsserv.nu",
"ns1.dnsserv.se"
]
} |
No. PhishDestroy classifies prozone.st as a blocklisted domain (risk: critical, 88/100); it was first detected on 2026-09-28. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on prozone.st. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
ns1.dnsserv.nuns1.dnsserv.seLocation describes the IP network.
780f931e53f6e66896c665aed92b4035fbe599f324bec8405045144c41510b62prozone.stSaved 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 prozone.st · checked Sep 28, 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.
cloudflare_challenge: raw=cf_challenge; http=200; via=https_proxy; server=BlazingFastWeb
prozone.st
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
3→4
2→3
1→2
0→1
No threat flag
View source5/92 engine detections
View source3 community references
View sourceprozone.st
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
prozone.st)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.