ERR_NAME_NOT_RESOLVED on Cloudflare
Why it happens on Cloudflare
A domain moved to Cloudflare resolves nowhere until the registrar's nameservers are changed — the DNS records exist in the dashboard but nothing on the internet is asked for them.
The fix on Cloudflare
In Cloudflare → DNS, confirm the assigned nameservers, then set exactly those two at the registrar. The lookup below shows which nameservers are authoritative right now.
Is ERR_NAME_NOT_RESOLVED happening on your domain?
Resolving the name from outside your machine shows whether public resolvers can find a record, helping distinguish a public DNS issue from a local resolver or network problem.
Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.
If that didn't fix it
Cloudflare has its own failure mode, but ERR_NAME_NOT_RESOLVED has a wider set of causes that apply everywhere. The most common one overall is: no dns record exists for the hostname.
All causes and fixes for ERR_NAME_NOT_RESOLVED