Error 530 is a composite error that Cloudflare returns alongside error 1016 (Origin DNS error). It indicates that Cloudflare was unable to resolve the hostname or IP address configured for the origin server. This typically happens when using Cloudflare with a CNAME setup and the CNAME target cannot be resolved, or when the DNS records in Cloudflare are misconfigured. The 530 is the HTTP-level error while 1016 provides the Cloudflare-specific explanation.
If your origin is configured as a CNAME (common with platforms like Heroku, AWS ALB, or Netlify), and that target hostname no longer resolves, Cloudflare returns 530/1016.
The A, AAAA, or CNAME record for the origin has been deleted from Cloudflare's DNS settings, or points to a hostname that does not exist.
If you recently changed the origin CNAME target, DNS propagation may not have completed, causing temporary resolution failures.
Verify that you have valid A, AAAA, or CNAME records pointing to your origin in the Cloudflare DNS dashboard.
Check DNS RecordsIf using a CNAME, check that the target hostname resolves to a valid IP address.
dig +short your-cname-target.example.com
If you recently changed DNS records, verify propagation is complete across global DNS servers.
Check PropagationIf the CNAME target is provided by your hosting platform (Heroku, AWS, etc.), verify the hostname is still valid and the application is deployed.
Cloudflare cannot reach the origin server because DNS resolution failed or the origin IP is unreachable.
Cloudflare received an empty, unknown, or unexpected response from the origin server.
The origin web server refused or is not accepting connections from Cloudflare.