1023: Could Not Find HostError 1023 is similar to error 1018 — Cloudflare received a request for a hostname that does not match any active zone. The difference is typically the context in which the error is triggered. Error 1023 commonly appears when the Cloudflare zone exists but the specific subdomain or hostname requested does not have any DNS records, or when a CNAME chain leads to a Cloudflare zone that has been deactivated.
Error 1023: Could Not Find HostGET /docs HTTP/1.1
Host: docs.example.com
User-Agent: Mozilla/5.0
Accept: text/htmlHTTP/1.1 409 Conflict
Server: cloudflare
CF-RAY: 7a1b2c3d4e5f6780-BNE
Content-Type: text/html
<!doctype html>
<html>
<head>
<title>docs.example.com | Error 1023</title>
</head>
<body>
<h1>Error 1023: Could not find host</h1>
<p>Cloudflare could not find a Cloudflare zone for this hostname. The domain configuration may be incomplete or the zone may have been removed.</p>
</body>
</html>Verify that a DNS record exists for the exact hostname returning the error (including the subdomain).
Check DNS RecordsLog into the Cloudflare dashboard and confirm the domain shows as Active, not Paused or Pending.
If the subdomain is missing, add an A or CNAME record in Cloudflare's DNS settings pointing to the correct origin.
The domain is active on Cloudflare, but there is no A, AAAA, or CNAME record for the specific subdomain being accessed.
The Cloudflare zone exists but has been paused by the account owner, or nameserver verification has lapsed.
A CNAME record chains through multiple hostnames, one of which points to a Cloudflare zone that no longer exists.
This reference was compiled from official RFCs, protocol specifications, and hands-on troubleshooting experience. AI tools were used primarily for formatting and organizing the content on the page.