Cloudflare Error 530: Origin Hostname Cannot Be Resolved

Error 530 is a Cloudflare status code that comes with a second, more specific number. Cloudflare's documentation says it indicates that Cloudflare is unable to resolve the origin hostname, and that the response body contains a 1xxx error code identifying the particular problem. The 530 is the header; the 1xxx code is the diagnosis.

Because the 530 page has no steps of its own in Cloudflare's docs, the useful work is reading the 1xxx code and following the right page. This page explains how to do that and what the common ones mean. Do not confuse it with the 52x family covered in Cloudflare 520-526 errors explained, which concern the connection after the hostname is resolved.

How to see the real code

The visible page may show only "Error 530" in some contexts, but the body of the response carries a line such as "Error 1016" or "Error 1001." Get it from the browser page itself, or fetch it:

curl -s https://example.com/ | grep -o -i -E "error (code )?1[0-9]{3}" | head
curl -sI https://example.com/ | head -n 15

The Cloudflare Error Checker does this check and extracts the Ray ID. The HTTP Status Checker confirms that the HTTP status is 530.

Which 1xxx code you probably have

The 1xxx page explains the actual issue. These are the ones most often seen alongside a 530:

Another 1xxx number can also appear, so match what you see to Cloudflare's current list rather than assuming one of these.

If you are a visitor

A 530 is a configuration issue on the site's side. Retry in a few minutes, since a DNS change might still be propagating, and contact the site owner if it persists. Include the 1xxx code and the Ray ID, because they tell the owner exactly where to look.

If you are the site owner

Step 1: identify the 1xxx code

Without it you are guessing. Get the code, then jump to the matching page. If the code is 1016, follow the 1016 guide. For 1033, follow the tunnel error page.

Step 2: check the DNS record that Cloudflare uses for the origin

Open the Cloudflare DNS tab for the failing hostname and ask: is the target a valid public IP, or does the CNAME target resolve? Verify the target from outside using the DNS Checker:

dig +short origin.example.net A
dig +short origin.example.net AAAA
dig +short www.example.com CNAME @1.1.1.1

If the CNAME target returns nothing (NXDOMAIN or an empty answer), Cloudflare has nothing to connect to. Typos, deleted records at another provider, and expired domains are the usual reasons.

Step 3: watch for expired or moved external domains

If the CNAME points to a hostname at another company, such as a hosting platform or a storage bucket, the target can disappear when a subscription ends or a project is deleted. The Dangling DNS Checker finds records that point to something that no longer exists; see also subdomain takeover and dangling DNS, which explains why leaving such records is a security risk, not only an availability one.

Step 4: check nameservers and recent changes

Confirm that your domain still uses Cloudflare's nameservers with the Nameserver Lookup. If someone changed nameservers or the registrar reset them, the zone you edit in Cloudflare may not be the live one. The DNS History tool can show what changed. Allow time for propagation after edits; see how long DNS propagation takes.

Step 5: for tunnels and SaaS setups

If the hostname is served through Cloudflare Tunnel, the 1xxx code will usually be 1033 and the fix is on the machine running cloudflared. If the domain points at a SaaS provider, the provider's configuration may be missing; ask them.

Why not just "fix DNS"?

Resolving the origin hostname is only one layer. After you correct the record, test the full path: the proxied hostname should return a normal status, and the origin should answer on the expected port. If you then see 521, 522 or 525, you have moved past DNS to the connection problem; see error 521 and error 522.

Next steps

• Extract the exact code with the Cloudflare Error Checker.
• Verify records with the DNS Checker.
• Review changes with DNS History.
• Learn the basics in DNS explained for website owners.
• Read Cloudflare DNS and SSL modes for correct record setup.

FAQ

Is a 530 a Cloudflare outage?

Usually not. It means a configuration or DNS problem for your hostname, and the 1xxx code in the body identifies it. Check Cloudflare's status page if many unrelated sites fail at the same time.

Why does the browser show only 530?

Some views display just the HTTP status. The 1xxx code is in the response body, so view the page source or fetch it with curl.

Does clearing cache help?

No. The problem is DNS resolution of the origin, not cached content.

Can a 530 appear after a domain transfer?

Yes, if records were not carried over or nameservers changed. Verify that the live zone still has the right records.

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.