Infrastructure
What happens between the tap and the page
A CTAurl short link redirect is one lookup and one HTTP 302 straight to your destination, unless a QR code is set to show a location-consent page first. The click is recorded after the redirect is sent, so counting never makes anyone wait.
Last reviewed 27 October 2026 by the CTAurl team
- Tap
buy-it.now/sneaker - Look upCloudflare finds the link and its current destination
- RedirectHTTP 302 to your page, straight away
- CountThe click is recorded after the redirect has gone
Where it runs
On Cloudflare's network
Every CTAurl short link is answered by a Cloudflare Worker on Cloudflare's network. Links and their destinations live in Cloudflare's database, and click counts in its analytics store. The app, this site and the redirects all run on the same provider.
Edits
A new destination applies to the next tap
On CTAurl, a new destination applies to the very next tap or scan, because each redirect reads the link's current destination. There is no cache to wait for and no propagation delay, and a printed QR code picks up the change without being reprinted.
Status codes
Why a 302, not a 301
Every active CTAurl short link answers with HTTP 302, which tells browsers and search engines the destination may change. A 301 would let browsers remember the old destination, and your edit would not reach everyone. A missing or disabled link answers 404 and is never cached.
A plain server-side redirect also suits link previews. Apple's developer documentation says Messages follows server-side redirects when it builds a link preview, but not meta or JavaScript redirects (Apple Developer Documentation, TN3156). With a 302 and no page in between, the preview can reach your destination.
| Request | Answer |
|---|---|
| An active link | 302 to the destination |
| A missing or disabled link | 404, not cached |
What we do not publish
CTAurl does not publish uptime percentages or speed figures, because it has not measured them in a way it would stand behind. There is no public status page. When those figures exist, they will appear here with the method.
Developer notes
Frequently asked questions
Is there a page between the tap and my destination?
A normal CTAurl link has no ad screen and no extra page: the person tapping gets a 302 straight to your destination. The one exception is a QR code you set to ask for location, which shows a consent page first. You choose that setting per code.
Do edits take time to reach everyone?
No. Each CTAurl redirect reads the link's current destination, so a saved change applies to the next tap or scan. There is no cache to clear. Because links answer with a 302, browsers are not told to remember the old destination either.