Domain Management Guide
The layer where synced inventory becomes something your team can actually review, organize, and operate.
Why the Domains Layer Matters
A flat list of domain names is not enough for production work. Teams need visibility, filtering, inspection, and a way to turn raw inventory into the foundation for everything downstream.
In 301.st, the domains layer is that foundation. It is where integrations become day-to-day operations.
What Operators Get
- Synced domain inventory from connected integrations.
- One table for review, filtering, inspection, and follow-up actions.
- A cleaner handoff into projects, sites, and redirect workflows.
- Less provider dashboard hopping when teams need the current operational picture.
What Good Domain Ops Looks Like
- Inventory is synced and trusted before downstream work begins.
- Teams can filter quickly to the slice of infrastructure they actually need.
- Domains are attached to structure only when that structure improves clarity.
Recommended Working Loop
- Connect Cloudflare or registrar-linked integrations.
- Sync domain inventory and confirm the expected assets appear.
- Use filters and inspection to understand operational state.
- Attach domains to projects or sites where structure is genuinely useful.
- Move into redirect workflows from a clean, trusted inventory base.
How Domain Management Connects to the Rest of the Product
- Projects: domains stop being loose inventory and become part of a working boundary.
- Sites: domains can be attached to clearer destination and routing context.
- Redirects: stable traffic workflows become easier once inventory is already organized.
- TDS: newer routing layers still depend on the same trusted domain foundation.
FAQ
Is this just a domain list?
No. The point is not storage, it is operational visibility and action on top of synced inventory.
Do domains have to live in Cloudflare?
Cloudflare is the main workflow, but registrar-linked inventory can still be useful for broader management and visibility.
Should I organize domains before redirects?
Yes. A clean domains layer makes redirect operations far easier to read, review, and maintain.