Error 1018 means that the hostname in the request does not match any active Cloudflare zone. The domain may have been recently added to Cloudflare but setup is not complete, the domain may have been removed from Cloudflare, or the DNS is pointing to Cloudflare's network but the zone does not exist. This differs from 1001 (DNS resolution error) because the domain reaches Cloudflare's network but there is no matching zone configuration.
The domain was deleted from the Cloudflare account but the nameservers at the registrar still point to Cloudflare, so requests arrive at Cloudflare with no zone to serve them.
The domain was added to Cloudflare but the nameserver change at the registrar was never completed, so Cloudflare has not activated the zone.
The domain's nameservers are set to Cloudflare nameservers assigned to a different account or a previous Cloudflare configuration.
Log into your Cloudflare dashboard and confirm the domain appears in your account with an Active status.
If you recently added the domain, update your registrar's nameservers to the ones Cloudflare assigned (shown in the dashboard) and wait for verification.
Verify the domain's nameservers match what Cloudflare assigned to your zone. Mismatched nameservers prevent zone activation.
Check DNS RecordsIf the domain was accidentally removed, add it back to Cloudflare and reconfigure the DNS records and settings.
Cloudflare's DNS could not resolve the requested hostname.
Cloudflare cannot resolve the origin server's DNS — typically shown alongside HTTP error 530.
Cloudflare could not find the requested hostname — the domain or zone configuration does not exist.