HTTP 530 Site Frozen / Origin DNS Error

What does HTTP 530 mean?

Cloudflare: the origin returned an error together with a 1xxx error code; Pantheon: the site is frozen. On Cloudflare a 530 is shown together with a 1xxx error (for example 1016 “Origin DNS error”), which explains the real problem. On Pantheon it means an inactive site was frozen.

5xx Server error: The request looked valid, but the server failed to fulfil it. The fix is on the server side.

Common causes of a 530 error

• Cloudflare cannot resolve the origin hostname (error 1016).
• A Cloudflare Tunnel is down.
• An inactive Pantheon sandbox site was frozen.

How to fix 530 Site Frozen / Origin DNS Error

• Read the accompanying Cloudflare 1xxx error code and fix the DNS record or tunnel it names.
• On Pantheon, unfreeze the site from the dashboard.

530 and SEO

Visitors and crawlers get an error page; fix it quickly.

Example response

HTTP/1.1 530 Site Frozen / Origin DNS Error

Related status codes

• 523 Origin Is Unreachable — Cloudflare could not reach the origin server at all.
• 521 Web Server Is Down — Cloudflare could not connect to the origin server — the connection was refused.
• 502 Bad Gateway — A gateway or proxy got an invalid response from the upstream server.

Check which status code a URL returns with the HTTP header checker.