Changelog

Host-only cookies were leaking to subdomains. We track the Domain attribute properly now and added an HO badge in the Parsed view for the (uncommon) host-only case. Raw view matches what the upstream sent: Domain=.example.com for domain cookies, no Domain= line for host-only.

The Browser endpoint accepts only eight inputs (url, userAgent, headers, cookies, proxy, timeout_ms, checkStatus, checkText). The playground had been showing extras like wait_selector and viewport that silently dropped on the wire. Every field is now schema-aligned: Browser forces GET, hides the body textarea, and the Raw tab shows the exact JSON that hits the API plus a curl reproducer.

Single and Proxy Finder were silently dropping the unblocker signature even when unblocker: true was set, so anti-bot walls that check the request signature were still bouncing requests. Fixed end-to-end — if you had unblocker: true and were getting blocked on Cloudflare-fronted sites, that is why.

Some Cloudflare sites return 200 OK but inject a background script that issues the real cf_clearance cookie a moment later. Browser used to return the page before that cookie arrived, leaving the jar empty. Now Browser waits for the cookie event, so you get a clean cf_clearance you can replay through Single or Proxy.

The Older button on the blog used to send you back to page 1. Pagination now lives at /blog/page/N/ URLs with numbered navigation, so you can actually browse older posts. Thanks, Vladimir Petrov.

Browser requests were silently going through our non-JS engine for 41 days. If you saw Browser fail on Cloudflare challenges or JS-heavy sites during that window, this was why. We fixed the routing. Browser hits real Chrome on every request again.

The dashboard preview on the homepage was cramped on small screens. We fixed the type and spacing, and added tooltips that actually work on touch (hover-only hints don't help a phone).

We found two ways a dead proxy could get pinned in the picker and never get evicted, which dragged response times under sustained load. Both are fixed. In our load tests, p95 dropped from over 5 seconds back to under 500ms and the fail rate went from 8% to zero.

If your sign-in used to land on a raw 400 page after a stale tab or a slow callback, that's fixed now. We detect the session mismatch, wipe the bad cookie, and send you back to the login screen. Cleanly, every time.

New proxies stay inactive in Proxy Finder until validation confirms they actually work. Before this fix, fresh imports could be picked for live requests before anyone confirmed they were responding, which dragged down first-attempt success rates. That path is closed now.

When your login cookie expired or two tabs raced the callback, you used to land on a raw white error page. Now we wipe the stale cookies and send you back to a fresh login form. Other auth errors (token failures, account issues, expired impersonation) get a proper branded page with a retry button instead of bare text.

Two fixes for the login flow. Pinch-zoom works again for low-vision users (the viewport no longer caps zoom at 1x). And the theme you picked elsewhere on foura.ai now carries through to login, signup, and recovery pages instead of resetting to your OS preference.

Your dashboard's Rate Limit column on the by-domain and top-clients tables had been rendering as "--" and clicking the header to sort did nothing. Both work correctly now. If you've been trying to spot rate-limited traffic across your domains, the numbers are finally there.

If the verify email didn't show up right away, some people clicked resend a few times and got four or five copies. We added a 60-second cooldown on the resend button and a 30-minute server-side cap. One resend is enough now, and your inbox stays clean.

If you started signing up from a specific page, the flow now brings you back there after email verification. Previously it dropped you on the homepage.