530 Site Frozen

The HTTP 530 status code is an unofficial server error used by Cloudflare, Pantheon, Shopify, and Edgio (formerly Layer0) with different meanings. Cloudflare pairs a 530 with a secondary 1XXX error code providing additional detail, Pantheon uses 530 Site Frozen to indicate an inactive site, and Shopify surfaces the code as 530 Origin DNS Error when Cloudflare is unable to resolve the origin DNS record for a Shopify store.

Table of Contents

Usage specific to Cloudflare

Cloudflare is a content delivery network acting as a reverse proxy between clients and origin servers. When Cloudflare returns a 530, a secondary 1XXX error code accompanies the response with a more specific explanation.

For example, 530 / Error 1016 Origin DNS Error means Cloudflare was unable to resolve the origin server's IP address through DNS. Other 1XXX codes cover issues such as banned IPs, access denied, and rate limiting.

Note

The secondary 1XXX error code determines the actual cause. The 530 status alone does not identify the specific problem.

SEO impact

Search engines treat 530 responses as server errors. Persistent 530 errors reduce crawl rate and prevent indexing of affected URLs. Resolving the underlying DNS, hosting, or platform issue restores normal crawling.

Usage specific to Pantheon

Pantheon is a web hosting platform for content management systems. When a Pantheon Sandbox site remains inactive for an extended period, the platform freezes the site and returns 530 Site Frozen for all incoming requests. Reactivating the site through the Pantheon dashboard restores normal operation.

Usage specific to Shopify

Shopify lists 530 Origin DNS Error in its API response codes documentation. The code originates from Cloudflare, which provides CDN and proxy services for Shopify stores. When Cloudflare is unable to resolve the DNS record for a Shopify store's origin, the response reaches the API consumer as a 530. The underlying cause and resolution are identical to the Cloudflare 530 / Error 1016 described above.

Usage specific to Edgio

Edgio (formerly Layer0/Limelight) returns 530 as a generic "Internal Edgio Error" for unexpected platform-level failures. Edgio generates 53x status codes when errors originate within the Edgio infrastructure rather than the origin server. A 530 indicates an unclassified internal failure distinct from more specific Edgio errors such as 533 (TLS mismatch) or 539 (project timeout).

Example

Cloudflare 530 with DNS error

A client requests a page through Cloudflare, but the origin's DNS record is misconfigured. Cloudflare returns a 530 with secondary error 1016.

Request

GET / HTTP/1.1
Host: www.example.re
Accept: text/html

Response

HTTP/1.1 530
Date: Sun, 02 Mar 2026 11:05:00 GMT
Content-Type: text/html
Server: cloudflare
CF-RAY: 8a1b2c3d4e5f6-MIA

<html>
<head><title>Error 1016</title></head>
<body>
<h1>Error 1016</h1>
<p>Origin DNS error</p>
</body>
</html>

Pantheon 530 Site Frozen

A client requests a page on an inactive Pantheon Sandbox site. The platform returns a 530 indicating the site is frozen.

Request

GET / HTTP/1.1
Host: www.example.re
Accept: text/html

Response

HTTP/1.1 530 Site Frozen
Date: Sun, 02 Mar 2026 11:06:00 GMT
Content-Type: text/html

<html>
<head><title>Site Frozen</title></head>
<body>
<h1>530 Site Frozen</h1>
<p>This site has been frozen due to inactivity</p>
</body>
</html>

How to fix

Cloudflare: The 530 status alone does not identify the root cause. Inspect the HTML response body for the accompanying 1XXX error code and follow the Cloudflare 1XXX error documentation for the specific code. Common pairings include:

  • 530 / 1016 (Origin DNS Error): The origin hostname does not resolve. Verify A, AAAA, and CNAME records in the Cloudflare DNS settings point to a valid, reachable IP address. Run dig against the origin hostname to confirm resolution.
  • 1000 (DNS points to prohibited IP): The DNS record points to a Cloudflare IP or a reserved address. Update the record to the origin server's actual IP. Often paired with 530, but the HTTP status code varies.
  • 1001 (DNS resolution error): Cloudflare was unable to resolve the CNAME target. Confirm the CNAME chain resolves end-to-end. Often paired with 530, but the HTTP status code varies.

For all Cloudflare 530 variants, check DNS records first, then verify the origin server is online and accepting connections from Cloudflare IP ranges.

Pantheon: Log into the Pantheon dashboard and reactivate the frozen site. Pantheon freezes Sandbox sites after extended inactivity. Upgrading the site plan to a paid tier prevents future freezes. Once reactivated, the site begins serving requests immediately without further configuration.

Takeaway

The 530 status code carries different meanings depending on the platform. Cloudflare accompanies the 530 with a secondary 1XXX error describing the specific issue, Pantheon uses 530 Site Frozen to block requests to inactive sites, and Edgio returns the code as a generic internal platform error.

See also

Last updated: March 5, 2026