Skip to content
NewA calmer, faster ZeroHour
Toolsinfo

Protected Quick Tunnels: simple accountless authentication for your next dev project

Cloudflare Blogby Nikita Cano ()7 min read10 · 4 reads
AI summary · grok-4.7Summaries by Vani AI

Cloudflare Quick Tunnels can now require email one-time PINs so accountless localhost previews are not publicly reachable.

Starting with cloudflared 2026.9.3, Quick Tunnels accept an --allowed-mail flag that limits a random trycloudflare.com URL to chosen email addresses or domains. Visitors enter a one-time PIN from Cloudflare Access, and cloudflared on the developer's machine authorizes the verified address; neither side needs a Cloudflare account. Omitting the flag leaves public Quick Tunnels unchanged. The same flow is available through wrangler tunnel quick-start, and Cloudflare says coding agents have sharply increased Quick Tunnel use.

Key facts
  • cloudflared 2026.9.3 adds --allowed-mail allowlists to Quick Tunnels.
  • Visitors prove email control with a Cloudflare Access one-time PIN.
  • Neither visitor nor operator needs a Cloudflare account.
  • Rules stay on the local machine; omitting the flag keeps tunnels public.
  • Wrangler quick-start can launch the same protected tunnel.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

7 min read at blog.cloudflare.com

Quick Tunnels now support email authentication. Add --allowed-mail to one cloudflared command, and only the addresses or domains you list can reach your local app. No Cloudflare account required on either side.

Cloudflare Blog

By Nikita Cano · blog.cloudflare.com

Read the full article at Cloudflare Blog

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.