530 Site Is Frozen / Cloudflare Error
Cloudflare pairs 530 with a specific 1xxx error code, and some platforms use it for a site frozen by the provider.
Status
HTTP/1.1 530 Site Is Frozen / Cloudflare Error
Details
- Category: 5xx
- Status: Unofficial (Cloudflare, Shopify). Not registered with IANA. A server, framework, or CDN convention.
- Specification: none, not defined by any RFC
- Cacheable: Not cacheable
- Response body: Allowed
- Retry: Retry only after changing the request
Cloudflare pairs 530 with an internal error number in the 1xxx range, and that number carries the real meaning. Error 1016 is an origin DNS failure, 1020 is a firewall rule block, and so on. The 530 by itself tells you almost nothing: read the body.
Separately, some hosting platforms use 530 to mean a site has been frozen, typically for non-payment or a terms violation.
Common causes
- A Cloudflare 1xxx condition such as an origin DNS error (1016) or a firewall block (1020).
- A worker exception or a configuration error at the edge.
- A hosting account frozen by the provider.
How to fix it
As the client
- Read the 1xxx error number in the body. That is where the diagnosis is.
- If it is 1020, the request was blocked by a firewall rule, which usually means the address or its fingerprint was flagged rather than the URL being wrong.
As the server
- Look up the specific 1xxx code in the CDN dashboard and fix the named condition.
- For DNS errors, check that origin records resolve and that the proxy status matches the intent.
Examples
GET / HTTP/1.1 Host: www.example.com HTTP/1.1 530 Server: cloudflare error code: 1020
Notes for proxy users
Cloudflare error 1020 behind a 530 is a firewall block on the requesting address. It behaves like a 403: change the source address and the request profile rather than the URL.