When a monitor reports HTTP 530, inspect the full Cloudflare response. Its body contains a more specific 1xxx error code that directs troubleshooting. Record the status and detailed message together: a status-only alert does not supply enough evidence for one universal WordPress repair.
Guide reviewed: October 8, 2026. Interface labels may vary by version, account and device.
Find the specific 1xxx error inside the 530 response
| Report | Next check | What to record |
|---|---|---|
| Only HTTP 530 shown | Full response body or screenshot | Detailed numbered code |
| Browser shows a specific 1xxx error | That error’s documented investigation | Hostname, time and Ray ID |
| Monitor and browser differ | Same URL and client configuration | Both results and request times |
| No detailed body available | Ask the provider or monitor for evidence | Original alert rather than a guessed cause |
Find the detail behind the status
Support record: failed URL, HTTP status, detailed code, full error text, Ray ID and time zone. For example, a detailed origin-DNS message leads to a destination review; another code may identify a different configuration. Preserve the actual number shown.
Open the affected public page and save the complete error text, including any numbered code and Ray ID. Note the exact hostname and time. If the report came from a monitoring service, ask for the response body or an error screenshot as well as its status summary.
For example, a monitor might label a page as HTTP 530 while the response itself reports an origin DNS error. That gives the administrator a DNS destination to review. A different 1xxx message would lead to a different investigation, so keep the number rather than replacing it with a generic outage description.
Do not assume that a successful test of another hostname explains this request. The root domain, www address, and an API subdomain may follow different configurations.
Use the specific error to choose the next check
For a detailed 1016 message, follow the origin DNS investigation. For 1001, use the DNS target-chain checks. Choose the guide from the response actually received rather than treating these examples as the only possible outcomes.
Cloudflare describes 530 in connection with resolving the origin hostname, but its documented troubleshooting instruction is to use the specific 1xxx code in the body. That detail should guide the next step rather than a list of unrelated WordPress changes.
When the detailed error concerns a missing or unsuitable DNS destination, compare the relevant record with the hosting provider’s current instructions. When it identifies a different Cloudflare configuration, give the responsible administrator that complete message.
For a provider-managed domain connection, the provider may control the destination or account configuration behind the failure. Tell it how the domain was connected and whether a recent migration or activation preceded the error.
Keep the change history close to the error report
A short timeline helps support connect the message with the configuration. Record the last known working time, the first observed failure, and any relevant DNS, account, or provider change between them.
For example, “the www hostname began failing after the new CNAME was saved” identifies a focused comparison. “All WordPress settings were changed while troubleshooting” makes that comparison much harder.
Save the existing configuration before a supported correction. If the host supplies a new destination, keep its instructions beside the previous value. This makes the test understandable and reversible.
Separate visitor observations from administrator work
A visitor can report the page address, time, and complete error screenshot. The owner or provider is responsible for the configuration. Repeated refreshing will not repair a DNS or account-side problem, and a visitor should not need to install a repair tool.
As the owner, avoid changing the theme, database, or plugin collection merely because a monitor shows 530. Those actions should be connected to evidence from the detailed error and the request path.
If no detailed code is available, keep the original response and ask the provider or monitoring service for more information. Guessing a specific cause from a status number alone can send the investigation in the wrong direction.
Verify the original URL after the repair
After the administrator makes the change indicated by the specific error, open the exact URL that failed. Confirm the expected WordPress content and another relevant page beneath the same hostname.
Check the monitoring service’s next result too if it raised the alert. A browser request succeeding is useful, but the original monitoring client may use a different address or configuration.
If another error appears, record its status and detailed message separately. The repair may have restored one stage of the connection while exposing a later issue. Keep those observations in order instead of assuming that every failure is still the original 530.
For support, provide the public hostname, HTTP status, detailed 1xxx code, Ray ID, failure time, and recent configuration changes. This gives the reviewer a specific problem to investigate and avoids an article or ticket that promises one universal 530 fix.
Reference: Cloudflare error 530 documentation.
Confirm both page and original monitor recover
Retest the failed URL and intended content, then review the monitoring client that raised the alert. Record any new status and detailed message separately. A later failure may be a different stage of the connection, and keeping the evidence in order makes support review clearer.