How to Fix Cloudflare Error 1014 (CNAME Cross-User Banned)
What Error 1014 means
Cloudflare's 1xxx error family covers DNS and proxy configuration problems, and Error 1014 is the one that says "CNAME Cross-User Banned." It means one of your domain's CNAME records points at a hostname that lives in a different Cloudflare account than yours. Cloudflare does not allow CNAME records to resolve across accounts, so instead of loading your website it serves the Error 1014 page.
This error is unusual because the hostname your CNAME points to can be perfectly fine on its own — the problem is the relationship between the two accounts. Nothing about your computer, browser, or internet connection causes it, and nothing on the visitor's side can resolve it. Only someone with access to the domain's Cloudflare DNS can fix the record. It is also worth distinguishing 1014 from its close relatives: Error 1011 blocks hotlink protection violations, Error 1018 means Cloudflare could not find the host at all, and Error 1000 means a record points at a prohibited Cloudflare IP.
Common causes
- CNAME pointing at a platform you do not own: the most common trigger. Pointing www at your website builder's domain, your email marketing platform's domain, or a landing-page tool's domain — when that target hostname sits in the platform's own Cloudflare account rather than yours, Cloudflare treats it as cross-user and blocks it.
- Leftover CNAME from an old host: moving away from a hosting provider but leaving a subdomain CNAME aimed at the old provider's hostname. The old hostname now resolves through someone else's Cloudflare setup, and your domain gets flagged.
- Incomplete platform onboarding: many SaaS platforms that ask you to CNAME to them use Cloudflare for SaaS, which requires you to add a verification record (often a TXT record) so their system can authorize your domain. If you added the CNAME but never completed the verification step, the cross-account link is never approved and visitors see Error 1014.
- Reseller or agency account split: a domain registered under one Cloudflare account and a service hostname managed under the agency's or reseller's Cloudflare account. The CNAME is technically correct but spans two accounts, which Cloudflare bans by default.
- Pointing at a third-party CDN or proxy hostname: aiming a CNAME at another provider's Cloudflare-fronted hostname (for example a partner's CDN endpoint) instead of at the origin they documented. The target's Cloudflare account is not yours, so the request is refused.
How to fix Error 1014 — step by step
Steps 1 through 5 are for the site owner. Step 6 is for visitors.
- Recognize that Error 1014 is an owner-side DNS problem. Error 1014 is served by Cloudflare only for domains already using Cloudflare, and it means one of the site's CNAME records points at a hostname owned by a different Cloudflare account. No browser setting, VPN, or device change can fix it — only the site owner (or their platform provider) can change the DNS records. Visitors should skip to step 6; the middle steps are for the site owner.
- Site owner: find the CNAME record that points at another Cloudflare user's hostname. Log in to the Cloudflare dashboard, select the domain, then go to DNS, then Records. Look for CNAME records — the classic culprit is the www record or a subdomain CNAME pointing at a hostname you do not own, such as a website-builder domain, a marketing platform domain, or an old host's domain. Note every CNAME record and its target before changing anything, so you can undo a mistake.
- Site owner: confirm the target belongs to a different Cloudflare account. Check the target hostname in a browser: if it loads a working site that is not yours and its DNS resolves to Cloudflare addresses, it belongs to someone else's Cloudflare account — that is the cross-user situation. If the target is your own host or platform's documented setup hostname, the connection may just be incomplete rather than truly cross-user, so check the provider's docs for a Cloudflare for SaaS or custom-hostname verification step you have not completed yet.
- Site owner: pick one of the three supported fix paths. Path A, simplest: move both domains into the same Cloudflare account — once the target hostname and your domain are under one account, the CNAME resolves normally. Path B: replace the offending CNAME with an A record that points directly at your provider's origin server IP (ask your host or platform for it), which removes the cross-account dependency entirely. Path C: complete your provider's official Cloudflare for SaaS setup — most platforms that need you to CNAME to them give you a verification record to add, such as a TXT record, which authorizes the hostname for your domain. Use the path your provider documents.
- Site owner: apply the change, verify propagation, then purge the cache. Edit or add the DNS record in Cloudflare and save it, keeping the proxy status (orange cloud) enabled unless your provider's instructions say otherwise. Wait for the change to propagate worldwide — usually minutes to a couple of hours — and check with an online DNS checker that queries from multiple locations that the hostname now resolves correctly. Then go to Caching, then Configuration in the Cloudflare dashboard and click Purge Everything, so cached copies of the Error 1014 page stop showing to visitors.
- Visitor: report it to the owner and retry later. As a visitor you cannot fix Error 1014 — the offending CNAME record lives in the site owner's Cloudflare DNS. Reload the page once to rule out a cached error, then reach the owner through their other channels: social media accounts, a contact email, or their support system. Tell them you are seeing Cloudflare Error 1014, which means one of their CNAME records points to a hostname owned by a different Cloudflare account — that phrase tells them exactly what to fix. Try the site again after a few hours; once the owner corrects the record and the cache is purged, the site loads normally.
Did this fix it? Quick checklist
- No CNAME record points at a hostname owned by a different Cloudflare account
- The platform's Cloudflare for SaaS verification (if required) is complete and confirmed
- A global DNS check shows the hostname resolving correctly from multiple locations
- After purging the Cloudflare cache, visitors load the site instead of the Error 1014 page
If you are the owner and the error persists after the records look right, double-check for a second CNAME you missed — apex and www are often configured separately, and subdomain CNAMEs pointing at third-party tools are easy to overlook. Also confirm the change is in the DNS zone that is actually active: if the domain's nameservers still point at the old host or registrar, your Cloudflare edits change nothing until the nameserver switch completes. And if a platform gave you a verification record, confirm it is present and matches their format exactly — one wrong character keeps the hostname unauthorized.
Frequently asked questions
What does Cloudflare Error 1014 mean?
Error 1014 means a CNAME Cross-User Banned situation: your domain has a CNAME record pointing at a hostname that belongs to a different Cloudflare account, and Cloudflare refuses to resolve CNAMEs across accounts. The message on the page reads: CNAME Cross-User Banned. It is a DNS configuration problem in the site's own settings, not a problem with your browser or connection.
Why does Error 1014 happen?
It happens when a CNAME record points at a hostname owned by someone else whose domain is also on Cloudflare — for example pointing www at your website builder's domain, your marketing platform's domain, or an old hosting provider's domain, when those hostnames sit in a different Cloudflare account than yours. It also happens when a platform's Cloudflare for SaaS setup is only half finished: the CNAME is in place but the verification record the platform requires has not been added.
Can I fix Error 1014 as a visitor?
No. The CNAME record causing the error belongs to the site owner's Cloudflare DNS, and only someone with access to that account can change it. Clearing your browser cache or switching networks will not help. The right move is to reload once, then contact the site owner through their social accounts or email, mention Cloudflare Error 1014, and try again in a few hours.
How do I know which CNAME record is causing Error 1014?
Open the DNS Records page for your domain in the Cloudflare dashboard and look at the CNAME entries. The suspect is any CNAME whose target you do not control — a third-party platform's hostname, an old host's domain, or anything that resolves to a Cloudflare address belonging to another account. Temporarily note each CNAME target, open it in a browser, and see whether it leads to a working site that is not yours.
Should I use an A record instead of a CNAME to avoid Error 1014?
Yes, when your host or platform gives you a fixed origin IP address — an A record points directly at the server and never depends on someone else's hostname, so the cross-user problem cannot happen. But follow your provider's official instructions: many platforms require a CNAME for load balancing or their Cloudflare for SaaS setup, and in that case the correct fix is completing their verification step, not forcing an A record against their guidance.