Evidence, not guesswork.

Troubleshoot Cloudflare and origin issues with evidence, not guesswork. Enter a domain to scan it, or paste an error code. Each result shows what was observed, what it most likely means, and how to confirm it yourself.

Error Code Lookup

example.comExample
DNS
example.com → 192.0.2.10
ok
TLS
TLSv1.3 · edge certificate valid
ok
HTTP
522 Connection timed out
fail

Likely cause

Cloudflare cannot establish a timely connection to your origin.

High confidence

Tools

Grouped by what you're trying to do.

Diagnose

Something is failing right now.

example.comExample

failHTTP 522 Connection timed out

Does your origin server respond fine when you bypass Cloudflare (hit it directly)?

YesNo

Scan Your Domain

Probe DNS, TLS and HTTP from outside your network and match what comes back to a likely cause.

Error Code Lookup

Already have the code or the browser message? Walk its decision tree to a fix.

Investigate

Find out why a request was blocked or challenged.

OWASP CRS ruleExample

942100 SQL Injection Attack Detected via libinjection

CRITICAL · paranoia level 1 · REQUEST-942-APPLICATION-ATTACK-SQLI.conf

Sent from your browser

User agent, screen size, timezone and language, WebGL vendor and renderer

WAF Rule Lookup

Map a Cloudflare WAF block to the OWASP CRS rule behind it, and decrypt the matched payload locally.

Rule data: OWASP CRS 3.3.10, the release Cloudflare's OWASP ruleset is based on

Fingerprint Checker

See the browser and connection signals a site's bot detection can read from you.

Prepare

Planning a move to Cloudflare.

SSL / TLS · 7 checks · 3 criticalExample

doneCertificate requirements identified

doneOrigin certificate validated

not doneCertificate chain tested

not doneSNI/hostname requirements checked

Migration Readiness

Check DNS, TLS, WAF, origin and rollback readiness before cutting over from FortiWeb, Imperva, Akamai, AWS or F5.

Learn

The reasoning behind the fixes.

GuideExample

Understanding HTTP 522

A 522 means Cloudflare couldn't even open a TCP connection to your origin.

Linked from 522 Connection timed out

Technical guides

Write-ups on TLS, DNS, WAF and Cloudflare errors, linked from the results they explain.

Common errors

How a result is built

Example: 522 Connection timed out Open this lookup
Observed
Cloudflare returned 522. You confirmed the origin responds when you bypass Cloudflare.
Interpretation
This pattern commonly indicates firewall or network filtering of Cloudflare traffic.
Likely cause
Cloudflare cannot establish a timely connection to your origin. High confidence
Check
Confirm your origin firewall or security group allows Cloudflare's published IP ranges.
Verify
Retry the request through Cloudflare and confirm the error is resolved.

Observed

A scan records facts first: DNS answers, TLS details, status codes and headers.

Interpretation

Results keep what was measured apart from what it suggests.

Likely cause

Those facts, plus anything you confirm, lead to a likely cause with a stated confidence, never a guaranteed root cause.

Verify

Every diagnosis ends with a check you can run yourself, so you can confirm it before you change anything.

What it can't tell you

  • A scan is one observation, made from our servers at one moment, not from where your visitors are.
  • Behind Cloudflare, your origin can't be probed directly. Some questions only you can answer.
  • Your origin's logs, firewall rules and Cloudflare dashboard settings aren't visible from outside.

Who runs this

21 error codes and 7 scan outcomes, each with a written decision tree. OriginError is an independent project, maintained by BIJODEV on GitHub. If a diagnosis looks wrong, report it.