Domain lifecycle

A RouteSeam domain is not simply on or off. It is a state machine: every domain sits in exactly one state, moves forward as verification and TLS provisioning succeed, and can move sideways into failure or administrative states. The status pill on the dashboard renders this state directly.

The happy path

flowchart LR
    PENDING_DNS --> DNS_VERIFIED --> TLS_PROVISIONING --> ACTIVE
    PENDING_DNS -.-> DNS_FAILED
    TLS_PROVISIONING -.-> TLS_FAILED
    DNS_FAILED -.-> PENDING_DNS
    ACTIVE --> SUSPENDED
    ACTIVE --> DISABLED

pending_dns — DNS Pending

The domain was just created, or DNS does not yet point at RouteSeam. RouteSeam shows you exactly one DNS record to add (an A record for an apex domain, or a CNAME for a subdomain) and checks automatically every few minutes.

Traffic redirects? No. The hostname is not yet in the edge configuration, so no certificate exists and no redirect is served.
What you can do: add the DNS record, then click Check DNS to verify on demand — or wait for the automatic sweep. See DNS setup.

dns_verified

The hostname resolves to RouteSeam infrastructure. A brief transition state: verification triggers TLS provisioning automatically.

Traffic redirects? Not yet — HTTPS is still being set up.
What you can do: nothing; this state usually lasts seconds.

tls_provisioning — Provisioning SSL

The domain has been published to the edge configuration, which is what authorizes RouteSeam to obtain its certificate. Issuance happens on the first HTTPS request; the control plane probes until the certificate serves correctly.

Traffic redirects? The first visitor’s HTTPS request triggers issuance, which takes a few seconds; from then on, redirecting works.
What you can do: wait. Provisioning normally completes in well under a minute.

active — Active

DNS is verified, the certificate is issued, and the redirect is live at the edge. This is the goal state — the mint-green moment.

Traffic redirects? Yes. Changes you make now (destination, status code, options) are live at the edge within seconds.
What you can do: edit the route, view analytics, or disable/delete the domain.

Failure states

dns_failed — DNS Failed

Verification failed — either the record was never added correctly, or DNS moved away from RouteSeam. Active domains are re-checked daily, so an active domain whose DNS breaks lands here too.

Traffic redirects? The domain is removed from the next edge configuration publish.
What you can do: fix the DNS record, then click Check DNS. A successful check moves the domain back toward active automatically.

tls_failed — SSL Failed

Certificate issuance failed after bounded retries. This is rare and almost always transient or DNS-related.

Traffic redirects? No — HTTPS cannot be served without a certificate.
What you can do: retry from the domain detail page; retrying moves the domain back to tls_provisioning. If retries keep failing, contact support. See DNS and TLS.

Administrative states

suspended — Suspended

RouteSeam has suspended the domain — typically in response to an abuse report or policy violation. Suspension takes effect within one configuration publish: routing and certificate renewal stop.

Traffic redirects? No, deliberately.
What you can do: this state is set by RouteSeam, not by you. If you believe the suspension is a mistake, contact support. See abuse and safety.

disabled — Suspended

The deliberate “off” switch: the domain is kept in your account with its configuration intact, but it is excluded from the edge.

Traffic redirects? No.
What you can do: re-enable the domain to send it back through verification and provisioning.

Status pill vocabulary

The dashboard uses one consistent pill vocabulary everywhere:

Pill	Meaning
Active	Live and redirecting
DNS Pending	Waiting for your DNS record
Provisioning SSL	Certificate being issued
DNS Failed	Verification failed — fix DNS and re-check
SSL Failed	Certificate issuance failed — retry
Suspended	Off — suspended or disabled, not serving

Domains and routes — what a domain and its route contain.
DNS and TLS — verification mechanics and certificate behavior in depth.
Quickstart — walk a domain through this lifecycle in about five minutes.