---
title: "530 Origin DNS Error — what it means and how to fix it"
description: "A Cloudflare error shown alongside a 1xxx error code that carries the real explanation. What causes an HTTP 530, what to try as a visitor, and what to check if it is your own site."
url: https://atoneplace.net/error/530/
site: "At One Place"
---

# 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

1. Look for the four-digit 1xxx error on the page — that is the code that actually explains the failure
2. 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

1. Read the accompanying 1xxx code first; 530 alone carries no diagnostic information
2. For 1016, check that every CNAME in your Cloudflare DNS resolves — a target at another provider that was deleted is the usual cause
3. If you use Cloudflare Tunnel, confirm the connector is running and healthy
4. 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](https://atoneplace.net/error/500/)
- [502 Bad Gateway](https://atoneplace.net/error/502/)
- [503 Service Unavailable](https://atoneplace.net/error/503/)
- [504 Gateway Timeout](https://atoneplace.net/error/504/)
- [524 A Timeout Occurred](https://atoneplace.net/error/524/)
- [521 Web Server Is Down](https://atoneplace.net/error/521/)
- [522 Connection Timed Out](https://atoneplace.net/error/522/)
- [520 Web Server Returned an Unknown Error](https://atoneplace.net/error/520/)
- [525 SSL Handshake Failed](https://atoneplace.net/error/525/)
- [526 Invalid SSL Certificate](https://atoneplace.net/error/526/)
- [501 Not Implemented](https://atoneplace.net/error/501/)
- [511 Network Authentication Required](https://atoneplace.net/error/511/)

## Sources

- Hypertext Transfer Protocol (HTTP) Status Code Registry — IANA (https://www.iana.org/assignments/http-status-codes/)
- RFC 9110: HTTP Semantics — IETF (https://www.rfc-editor.org/rfc/rfc9110.html)