Every redirect on the internet ends in a status code. Ours is 301 Moved, so introducing ourselves by moving in here felt about right.
Permanently
We write about the least glamorous corner of the web: redirects, DNS, and
HTTP on Cloudflare. The stuff nobody thinks about until a domain that
"definitely still redirects" quietly starts returning a 522, and a customer
emails you the screenshot.
Why we exist: we got tired of guides that were correct in 2021. Cloudflare
changes limits and retires products faster than tutorials get rewritten. The
docs promise 10,000 bulk redirects on the free plan; plenty of accounts open
the dashboard and find 20. So we check every number against the live docs and
stamp each article with the date we checked it. If a post doesn't say when it
was verified, assume it's quietly lying to you. Ours say. We are, admittedly,
a little paranoid.
What you'll get from us here:
- Why a redirect that looks perfectly configured still returns a
522, a525, or a registrar parking page — three different lies, onecurl. - Which of your 300 domains still redirect, and what to fix first.
- How to count a click on a redirect that never runs a line of JavaScript.
- The occasional existential post, like the time an "AI readiness" scanner scored our own docs site 21 out of 100 and we had to agree with most of it.
Full disclosure, because DEV is a place that likes it: this account is the
blog behind 301.st, a platform for managing redirects at
scale. That's the thing that made us this strange about DNS. But every article
solves your problem first and only mentions the product where Cloudflare's
native path actually runs out. You get the working answer either way.
Everything is also mirrored at 301.sh with plain markdown
versions for the LLMs, because it's 2026 and even the robots deserve readable
docs.
Say hi, and tell us your worst redirect story. We collect those. 👋
P.S. If this post ever 404s, we know, and we're deeply ashamed.
