Error 530: Origin DNS Error (Cloudflare)
Updated Free mock REST & WebSocket APIs
Error 530 Origin DNS Error — Cloudflare returns 530 together with a 1xxx error, most often 1016 (origin DNS error).
- Class
- 5xx Server Error
- Defined in
- Unofficial (Cloudflare)
- Official
- No — Cloudflare-specific
- Cacheable by default
- No (unless Cache-Control/Expires say so)
- Safe to retry
- Sometimes — idempotent requests only
Try it: get a real 530 response
Our test endpoint answers every request with 530 Origin DNS Error.
curl -i https://mockfox.dev/api/status/530Use it in tests, health-check monitors or to see how your client handles a 530. Add ?delay=2000 to slow it down.
What does Error 530 mean?
The page shows the real cause as a Cloudflare 1xxx error: 1016 means the origin hostname in your DNS record (often a CNAME) doesn't resolve; 1033 means a Cloudflare Tunnel isn't connected. Fix the DNS record or restart cloudflared. On some other platforms 530 is used for "site frozen" (Pantheon).
How to fix 530
- Visitors: This is a server-side problem — wait a moment and retry, or check the site's status page.
- Developers: Check application and proxy logs at the time of the error, verify upstream services are healthy, and alert on 5xx rates.
Example 530 response
HTTP/2 530 server: cloudflare cf-ray: 8d2f1a3b4c5d6e7f-AMS content-type: text/html; charset=UTF-8
5xx Server Error: The server failed to fulfill a valid request — usually temporary, or a server-side bug. See the full list of HTTP status codes.
Related status codes
- 523 Origin Is UnreachableCloudflare couldn't reach the origin at all — usually a DNS or routing problem.
- 521 Web Server Is DownCloudflare couldn't connect to the origin because it refused the connection.
- 502 Bad GatewayA gateway or proxy got an invalid response from the upstream server.
Related tools
Frequently asked questions
What does Error 530 Origin DNS Error mean?
Cloudflare returns 530 together with a 1xxx error, most often 1016 (origin DNS error).
Is 530 a client or a server error?
530 is a 5xx code: the server failed to handle a request that may be perfectly valid. It's often temporary.
Is 530 an official HTTP status code?
No. It isn't in the IANA HTTP Status Code Registry; it's specific to Cloudflare. Generic HTTP clients treat it as an unknown 5xx status.
How can I test how my app handles a 530?
Call https://mockfox.dev/api/status/530 — it responds with 530 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.