530 is a Cloudflare-specific code that Cloudflare returns together with one of its 1xxx errors. The 1xxx number, shown on the error page or as error code: 1016 in a plain-text body, identifies the actual problem; Cloudflare does not give 530 itself a name.
Common combinations are error 1016 (Origin DNS error), where Cloudflare cannot resolve the origin host name configured in a CNAME record, and error 1033 (Cloudflare Tunnel error), where the tunnel daemon cloudflared that connects the origin to Cloudflare is not running or not connected. Other 1xxx errors, for example with Workers, Pages custom domains or SaaS host names, can come with a 530 as well.
Example response
HTTP/1.1 530
Date: Fri, 06 Nov 2026 10:15:32 GMT
Content-Type: text/plain; charset=UTF-8
Content-Length: 16
Connection: close
X-Frame-Options: SAMEORIGIN
Referrer-Policy: same-origin
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Server: cloudflare
CF-RAY: 8f3a1b2c4d5e6f77-IAD
error code: 1016SEO and redirect checking
Like other origin errors, 530 makes the site unreachable for visitors and crawlers. Look up the 1xxx code from the error page in Cloudflare's documentation. For 1016, fix the DNS target; for 1033, restart cloudflared and check the tunnel's status in the Cloudflare dashboard.
Common causes and use cases
- A CNAME at Cloudflare points to a host name that no longer resolves (error 1016).
- The Cloudflare Tunnel daemon
cloudflaredis stopped or disconnected (error 1033). - A custom domain for a Pages project or a Worker is misconfigured.