HTTP 530 — Origin DNS Error
HTTP 530
Origin DNS Error
A Cloudflare error shown alongside a 1xxx error code that carries the real explanation.
What 530 actually means
Not an HTTP status code but a Cloudflare one, and an unusual one: a 530 is always accompanied by a Cloudflare 1xxx error displayed on the page, and that number is where the actual meaning lives. The most frequent pairing is error 1016, "Origin DNS error", where a CNAME in the Cloudflare DNS points at a hostname that will not resolve. Always read the 1xxx code on the page rather than the 530.
Common causes
- Error 1016 — a CNAME record pointing at a hostname that does not resolve
- A Cloudflare Worker throwing an unhandled exception (error 1101)
- A DNS record for a subdomain that was never created at the target provider
- A Cloudflare Tunnel that is not running or is misconfigured
If you're just trying to view the page
- Look for the four-digit 1xxx error on the page — that is the code that actually explains the failure
- Nothing else to do on your side; report it to the site owner with both numbers and the Ray ID
If it's your site
- Read the accompanying 1xxx code first; 530 alone carries no diagnostic information
- For 1016, check that every CNAME in your Cloudflare DNS resolves — a target at another provider that was deleted is the usual cause
- If you use Cloudflare Tunnel, confirm the connector is running and healthy
- For Worker errors, check the Worker's logs and exception handling
Reference
- Status code
- 530
- Reason phrase
- Origin DNS Error
- Category
- 5xx — Server Error
- Cacheable by default
- No
Common questions
- What does HTTP 530 mean?
- A Cloudflare error shown alongside a 1xxx error code that carries the real explanation. Not an HTTP status code but a Cloudflare one, and an unusual one: a 530 is always accompanied by a Cloudflare 1xxx error displayed on the page, and that number is where the actual meaning lives. The most frequent pairing is error 1016, "Origin DNS error", where a CNAME in the Cloudflare DNS points at a hostname that will not resolve.
- How do I fix a 530 error?
- Look for the four-digit 1xxx error on the page — that is the code that actually explains the failure
- Is 530 a client error or a server error?
- 530 is in the 5xx range, which means server error. The request was acceptable but the server could not fulfil it, so retrying later can succeed.
Related pages
- 500 Internal Server Error Something went wrong on the server and it has no more specific code to describe
- 502 Bad Gateway A proxy or gateway reached the server behind it and got back a broken response,
- 503 Service Unavailable The server is temporarily unable to handle the request, usually because it is ov
- 504 Gateway Timeout A proxy or gateway waited for the server behind it and gave up before an answer
- 524 A Timeout Occurred Cloudflare connected to the origin successfully but the origin did not finish re
- 521 Web Server Is Down Cloudflare could not connect to the origin server because it refused the connect
- 522 Connection Timed Out Cloudflare tried to open a connection to the origin server and never got a reply
- 520 Web Server Returned an Unknown Error Cloudflare reached the origin server but got back a response it could not make s
- 525 SSL Handshake Failed The TLS handshake between Cloudflare and the origin server failed.
- 526 Invalid SSL Certificate The origin server presented a TLS certificate that Cloudflare could not validate
- 501 Not Implemented The server does not support the functionality needed to fulfil the request, usua
- 511 Network Authentication Required You need to log in to the network itself — this is a captive portal, not the sit