530: Shown alongside a 1xxx error
A 530 is never the real error — Cloudflare always prints a 1xxx code with it. Which one is on the page?
1016 — Origin DNS error
The 530 is a wrapper. The 1016 is the actual failure: Cloudflare could not resolve an address for your origin, so it never reached your server at all. That is almost always a CNAME pointing at a hostname that no longer resolves, or a missing DNS record for the hostname being requested.
Check
Look at the DNS record in Cloudflare for the exact hostname that failed, and note whether it is a CNAME, an A/AAAA record, or absent.
Fix
Work through the 1016 guide at originerror.com/errors/1016 — it branches on which of those three you have, since the fix differs for each. In short: if it is a CNAME, resolve its target and confirm that target still exists; if there is no record, create a proxied one pointing at your origin.
Verify
Once the hostname resolves to a Cloudflare address, reload the site and confirm both the 530 and the 1016 are gone.
1015 — You are being rate limited
The 530 is a wrapper. The 1015 is the actual failure: a rate limiting rule on the zone matched this traffic and is throttling it. Nothing is wrong with your origin — Cloudflare is deliberately refusing requests at the edge.
Check
Open Security → Events in the Cloudflare dashboard, filter to the affected path, and find which rate limiting rule is matching.
Fix
Work through the 1015 guide at originerror.com/errors/1015. Either raise the threshold, narrow the rule so it stops matching legitimate traffic, or — if the requests really are yours — spread them out or route them through a path the rule doesn't cover.
Verify
Retry the request and confirm it is no longer refused, then watch Security → Events to check the rule has stopped matching normal traffic.
1020 — Access denied
The 530 is a wrapper. The 1020 is the actual failure: a WAF custom rule, firewall rule, or Access policy on the zone blocked this request. As with 1015, your origin was never contacted.
Check
Open Security → Events, find the blocked request by its Ray ID, and read which rule produced the block action.
Fix
Work through the 1020 guide at originerror.com/errors/1020. If the blocked request was legitimate, scope an exception to the specific rule rather than disabling the ruleset. If the rule that fired is from the managed OWASP ruleset, originerror.com/waf-rules will decode its rule ID and show what the pattern actually matches.
Verify
Retry the original request and confirm it is allowed, then check Security → Events to see the rule no longer matching it.
A different 1xxx code, or I can't find one
A 530 on its own says only that Cloudflare returned an error it wrapped — the paired 1xxx code is the entire diagnostic content, and there is nothing useful to conclude without it.
Check
The code appears on Cloudflare's error page under the 530, usually as 'Error 1xxx'. If the page is styled or intercepted and you can't see it, request the URL with curl — the code appears in the response body, and the Ray ID in the headers lets you find the same event in Security → Events.
Fix
Once you have the code, look it up directly at originerror.com/errors/ followed by the number. We currently cover 1015, 1016 and 1020 in full. For other 1xxx codes, Cloudflare's own reference at developers.cloudflare.com/support/troubleshooting/http-status-codes/ lists them all — we would rather point you there than pretend to a guide we haven't written.
Verify
You have what you need once you can name the 1xxx code; look that code up and follow its own Check, Fix and Verify steps.
Want to narrow it down interactively instead? Use the error lookup tool.