Origin DNS Error / Site Is Frozen
Production Risk
High — entire site is inaccessible. Fix DNS or reactivate the account immediately.
530 is used in two contexts: Cloudflare returns it as a 1xxx sub-error wrapper (the actual sub-error is in the response body) typically for origin DNS failures; Pantheon hosting uses it to indicate a site has been frozen due to inactivity or account issues.
- 1Cloudflare: The origin's DNS record cannot be resolved — the hostname configured in Cloudflare's DNS does not exist or returns NXDOMAIN.
- 2Cloudflare: DNS propagation has not completed after a recent DNS change.
- 3Pantheon: The site has been frozen due to plan expiry or inactivity on a free plan.
- 4Pantheon: Billing issue has caused the account to be suspended.
The DNS A record for the origin was deleted; Cloudflare cannot resolve the origin hostname.
# Cloudflare DNS lookup for origin → NXDOMAIN # Response body contains the actual 1xxx sub-error code
expected output
HTTP/1.1 530 (Cloudflare origin DNS error or Pantheon frozen site)
Fix 1
Fix origin DNS record in Cloudflare (Cloudflare context)
WHEN The origin DNS lookup is failing.
# Cloudflare dashboard → DNS → ensure A record for origin is correct # Check the 1xxx error in the response body for specifics
Why this works
Restores the DNS record so Cloudflare can resolve the origin hostname.
Fix 2
Unfreeze the Pantheon site (Pantheon context)
WHEN The site is hosted on Pantheon and has been frozen.
# Log in to Pantheon dashboard → Sites → unfreeze or upgrade plan
Why this works
Reactivates the site on Pantheon's infrastructure.
Cloudflare 530 always contains a 1xxx sub-error code in the response body with the specific reason.
Site frozen due to inactivity on free tier or billing issue.
Cloudflare 5xx error documentation
https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#530 ↗Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev