Cloudflare error 1097 is an onboarding restriction, not a WordPress file error. Changing plugins, themes or database settings will not establish why Cloudflare declined the domain addition.
Preserve the complete message and prepare a concise review request that explains your relationship to the domain, its current registration status and the setup step that produced the error.
The useful work is to explain your relationship with the domain and keep the current site connection stable. The message alone does not confirm a particular reason for the restriction or a review deadline.
Guide reviewed: October 8, 2026. Interface labels may vary by version, account and device.
Preserve the restriction message before requesting review
| Prepare | Include | Purpose |
|---|---|---|
| Your role | Owner, authorized manager or developer | Explain the connection to the domain |
| Attempt | Main domain, full error and time | Identify the exact setup result |
| Context | Direct or hosting-partner onboarding | Explain the workflow used |
| Current service | Whether the existing site works | Distinguish onboarding from downtime |
| Contact route | Current error and official guidance | Use the appropriate review channel |
Read the complete message before changing anything
A useful initial description is: “I manage this domain for its owner. Adding the main domain returns 1097 at the time noted below. The existing website remains available through its current DNS provider.” Adapt those facts to your actual situation; do not claim ownership or authorization you do not have.
Several domain-addition failures can look similar in a setup dashboard. A missing registration record, an incorrectly entered subdomain and a restricted web property require different responses. The number 1097 and the accompanying text are the details that identify this particular issue.
Keep a screenshot and note the domain you were trying to add. If the entry contains a page path or a www prefix, compare it with the registered main domain. Correcting an obvious input mistake is sensible, but a continuing 1097 result should still be handled through the review process described by Cloudflare.
The error does not provide enough information to conclude why the restriction exists. Avoid treating speculation about a previous owner, an earlier account or a permanent ban as a confirmed explanation. The review team can assess the domain and the request.
Explain your connection to the domain clearly
- State your role in one sentence.
- Identify the registered domain and intended setup.
- Include the full error and attempt time.
- Describe a recent acquisition or transfer only if relevant.
- Follow any verification request through the official review process.
A useful review request begins with your role. You might own the domain, manage the website for its owner or be responsible for a client’s technical setup. Describing that relationship in plain language helps the reviewer understand why you are asking to add the property.
For example, a developer could explain that the business owner has asked them to move an existing WordPress site to Cloudflare and that adding the registered domain returns 1097. An owner could state that they control the domain and are setting up their own website. Neither explanation needs a long history of unrelated hosting problems.
Include the exact error, the approximate time it appeared and whether the site is currently operating through another DNS service. Those facts connect the review request to the actual setup attempt. If the domain was recently acquired or transferred, mentioning that context may help explain your present relationship with it.
Use the contact route shown by Cloudflare
The official guidance identifies abusereply@cloudflare.com for non-Enterprise customers and the account team for Enterprise customers. Before contacting anyone, compare that route with the current message in your own dashboard and the linked documentation. A third-party forum reply is not a substitute for the service’s own instructions.
Use the normal review process for any ownership verification the team requests. A general explanation should not contain passwords, two-factor codes or registrar login details. Sharing those credentials would not help describe the error and would introduce an unnecessary account risk.
This article explains how to prepare the request; it cannot promise that the restriction will be removed or give a guaranteed review time. The decision belongs to Cloudflare, and the information requested may depend on the property involved.
Keep a working DNS setup in place while waiting
If the website already works through another provider, there is usually no reason to interrupt that connection merely because a new zone could not be added. Keep track of the current DNS records and the host’s required destination so the planned move can resume when the onboarding issue is resolved.
Changing nameservers to an unprepared destination can produce a new access problem for visitors. Deleting website or email records is also unrelated to resolving the review restriction. Treat the failed addition and the existing live website as separate parts of the work.
For a new site that has not launched, the host may offer a temporary address for preparation. That lets you work on the WordPress content while the domain setup is reviewed, without presenting the temporary address as a completed custom-domain launch.
Resume setup with a fresh connection check
If the domain can later be added, compare the new zone with the existing records before completing the DNS change. Then test the normal HTTPS address, the www version if used and a second page. A successful review resolves the onboarding obstacle; the website connection still deserves its own check.
Cloudflare lists error 1097 and its contact route in the domain-addition troubleshooting guide. For problems that arise after DNS is active, our WordPress DNS guide covers the next stage of website access.
Resume from an approved setup, not a guessed workaround
Keep the request and response with your migration notes. If onboarding later succeeds, review the DNS records and then verify the HTTPS site. Repeated unrelated configuration changes make a review harder to explain and do not establish that the restriction has been resolved.