New: Connect AI assistants via MCP

HTTP 5xx

530 Origin DNS Error

A Cloudflare-specific code served with an accompanying 1XXX error: Cloudflare answered but could not resolve or reach the origin behind it. Most often the 1XXX code is 1016 (origin DNS error) or 1033 (Cloudflare Tunnel unavailable); some Cloudflare-partnered hosts also serve 530 for frozen or suspended sites.

5xx Server error

What causes it

  • The DNS record Cloudflare uses for the origin is missing or points at a dead address, a cloudflared tunnel is disconnected, or the hosting account behind Cloudflare was suspended.

How to fix it

Open the URL in a browser and note the 1XXX code on the Cloudflare error page, then check the origin DNS records in the Cloudflare dashboard, confirm any cloudflared tunnel is connected, and verify the origin host still exists and the account is in good standing.

Example response

A typical raw HTTP response a client receives for a 530, with the headers this code is defined around. 

HTTP/1.1 530 Origin DNS Error
Content-Type: text/html; charset=utf-8

Related codes

500Common
Internal Server ErrorA generic server-side error. Something failed on the server and it could not complete the request.
501
Not ImplementedThe server does not support the functionality required to fulfill the request.
502Common
Bad GatewayA server acting as a gateway or proxy got an invalid response from the upstream server it was trying to reach.
503Common
Service UnavailableThe server is temporarily unable to handle the request, usually because it is overloaded or down for maintenance.
504Common
Gateway TimeoutA gateway or proxy did not get a timely response from the upstream server.
505
HTTP Version Not SupportedThe server does not support the HTTP protocol version used in the request.

Know before your visitors do.

Sentinel checks your site around the clock from multiple regions and alerts you the moment it starts returning a 5xx error, so you can fix it before it costs you.

Start monitoring free