resolved
Cloudflare
cloudflare.com/{account-id}
landed in 38msBookSlash for Cloudflare · Engineering
b/cf.
b/dns. b/workers.
Cloudflare URLs are buried under multi-segment paths: account ID, zone ID, sub-route. BookSlash gives the DNS console, Workers dashboard, security tab, and analytics each a flat name your team types.
cf
other shortcuts you might save
b/cfb/dnsb/workersb/r2
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Cloudflare, with notes on why each one survives the URL changes that break personal bookmarks.
- b/cf
Cloudflare dashboard root.
Universal entry point for engineers and ops.
https://dash.cloudflare.com/{account-id} - b/dns
DNS records for the primary zone.
Replaces a fragile bookmark to a 100-character Cloudflare URL.
https://dash.cloudflare.com/{account-id}/{zone-id}/dns/records - b/workers
Cloudflare Workers projects.
Engineers reach it for every Workers deploy.
https://dash.cloudflare.com/{account-id}/workers - b/r2
R2 storage buckets.
Object-storage URLs are deeply nested; the slug skips the navigation.
https://dash.cloudflare.com/{account-id}/r2/buckets - b/cf-analytics
Cloudflare Analytics dashboard.
Engineering and security reach it daily.
https://dash.cloudflare.com/{account-id}/{zone-id}/analytics/traffic - b/cf-security
WAF / security event dashboard.
Security incident response always opens with this URL.
https://dash.cloudflare.com/{account-id}/{zone-id}/security/events
Common workflows
Three patterns that pay back in week one.
01
DNS change management
Ops engineers reach b/dns for every DNS change. The slug stays consistent; the audit log records every BookSlash slug change for compliance evidence.
02
Workers deploy debugging
After a Workers deploy, engineers reach b/workers to verify health and inspect logs. Pairs with b/cf-analytics for traffic verification.
03
Security event response
When security alerts fire, b/cf-security lands the responder on the WAF event dashboard. The slug ends the multi-click navigation through Cloudflare’s sidebar.
With and without
Same Cloudflare. Different team experience.
Without shortcuts
Each engineer bookmarks Cloudflare with personal account/zone IDs. Cross-team handoffs include 100-character URL pastes. Security responses lose 30 seconds to navigation.
With BookSlash
b/cf, b/dns, b/workers, b/r2, b/cf-analytics, b/cf-security. Six slugs cover Cloudflare for engineering, ops, and security.
Frequently asked
BookSlash + Cloudflare
Namespace per account: b/cf-prod, b/cf-staging. The b/ pattern stays consistent; the segment after disambiguates accounts.
No — slugs are URL → URL. Automation lives in your CI/scripts using Cloudflare’s API directly. BookSlash gets engineers to the right dashboard view.
Each lives at its own URL. b/workers for Workers; b/pages for Pages projects.
Zero Trust URLs are at one.dash.cloudflare.com. Namespace: b/zt-policies, b/zt-applications. The b/ pattern carries.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial