Cloudflare HTTP 530 (with Error 1016 Origin DNS error / 1033 tunnel error)
Cloudflare returns 530 together with a 1xxx error; the 1xxx code (usually 1016 or 1033) tells you the real cause.
Seen on:
Cloudflare
Meaning
530 is a wrapper status: Cloudflare couldn’t resolve or reach the origin. 1016 means the origin hostname (CNAME target) doesn’t resolve; 1033 means a Cloudflare Tunnel isn’t connected.
Common causes
- Origin CNAME target doesn’t resolve (1016)
- Cloudflare Tunnel down (1033)
- DNS record deleted at the origin provider
⚡ Quick fix
- Read the 1xxx code on the page and follow that fix
- Check the CNAME target resolves publicly
- Check cloudflared status
Detailed fix by platform
Shell
- bash
dig +short CNAME app.example.com @1.1.1.1 dig +short origin.provider.net @1.1.1.1
How to diagnose
- Code — Which 1xxx code appears?
- DNS — Target resolves?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Cloudflare
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026