Getting Started With 301.st

Sign-up to first live redirect in under 10 minutes if you already have a Cloudflare account. Everything below is what each step actually unlocks — not just what to click.

Five Steps to Production

  1. Create access. Sign in with email or OAuth and make sure the account you use matches the team that will own operations.
  2. Connect Cloudflare. This is the trust boundary that unlocks zone discovery, domain sync, and routing workflows.
  3. Sync domains. Pull real inventory into the domains layer before trying to model downstream logic.
  4. Create structure. Use projects and sites when you need clear boundaries for brands, offers, teams, or destinations.
  5. Launch redirects. Treat redirects as the main stable production workflow once the foundation is clean.

Start Here If

  • You run 20+ domains across one or more Cloudflare accounts and the per-zone UI is now the bottleneck.
  • You manage multiple brands or clients and need isolation between projects without separate Cloudflare accounts.
  • You want to evaluate with minimal risk — connect one Cloudflare account, sync a handful of domains, ship a single redirect, decide.

Skip If

  • You only have one or two domains — Cloudflare Page Rules cover that case cheaper.
  • You are not on Cloudflare. 301.st reads and writes through the Cloudflare API; we do not currently support Route 53 / Vercel / Netlify equivalents.
  • You want to migrate DNS away from Cloudflare. That is the opposite direction.

What Is Built

  • Auth: email + password, OAuth (Google / GitHub / Yandex), multi-method sign-in management.
  • Integrations: Cloudflare (token-based, multiple accounts), Namecheap, NameSilo, VirusTotal.
  • Domains: filterable table, per-domain inspector, bulk re-sync / block / assign-to-project / attach-to-site, subdomain create + delete.
  • Routing: redirects with T1–T7 templates and version-aware bulk sync; TDS Smart Shield (geo/device/bot) and SmartLink (UTM/click-ID) rules deployed to Cloudflare Workers.
  • Attribution: postback sources with per-event URLs, live conversions dashboard, drop-in support for 1Win-class operators and traditional networks. Self-service billing and plan management.

What Catches People Out

  • First Cloudflare sync on a fresh integration with many zones can take a couple of minutes — be patient on the initial run; subsequent syncs are fast.
  • Stripe is unavailable in the RU region (blocked at the network level); the Russian deploy at 301.ru uses Cryptomus and YooKassa instead.
  • TDS rules deploy to a Cloudflare Worker on your acceptor domain — Free plan Worker request quotas apply to your traffic. Workers Paid is recommended once volume scales.

FAQ

Do I need Cloudflare?

Yes. 301.st operates on top of Cloudflare zones — redirects and TDS rules are deployed there. Other DNS providers are not currently supported.

Can I skip projects and sites?

Yes — they are optional. You can create redirects directly against synced domains. Add projects/sites later when you need isolation between brands, clients, or environments.

What is the difference between Redirects and TDS?

Redirects are unconditional URL → URL rules — what Page Rules and Bulk Redirects do, plus versioning and bulk apply across zones. TDS adds conditional routing: Smart Shield filters by request signals (geo, device, bot detection); SmartLink routes by URL parameters (utm_source, fbclid, gclid, sub-IDs). Start with Redirects; add TDS when a use case actually needs the conditions.

Next Guides

Cloudflare integration Domain management Projects and sites Redirects TDS rules