Quickstart

This guide walks you from a fresh account to a live HTTPS redirect in about five minutes, excluding DNS propagation time.

Before you start

You need a domain you own, access to its DNS provider, and a destination URL. See the overview for details.

1. Sign up

Create a RouteSeam account with your email and password, then verify your email address. A workspace is created automatically — there is no organization setup step.

2. Add your domain

From the dashboard, click Add Domain and fill in the form:

• Source domain — the hostname you want to redirect from, e.g. oldcompany.com
• Redirect destination — the full URL to send traffic to, e.g. https://newcompany.com
• Redirect type — defaults to 308 Permanent Redirect, which is permanent and preserves the request method. Choose 301/302/307 if your workflow calls for it; see redirect types.
• Options — preserve path, preserve query parameters, and redirect www are enabled by default.

RouteSeam validates the hostname, checks it isn’t already claimed, validates the destination URL, and rejects configurations that would create a redirect loop.

Your domain is created with the status DNS Pending.

3. Add the DNS record

RouteSeam shows you exactly one record to create:

Type	Name	Value
A	@	the RouteSeam edge IP shown in your dashboard

Subdomains get a CNAME instead of an A record — the dashboard shows the right one for your hostname. Add the record at your DNS provider. For a detailed walkthrough of apex vs. subdomain records, see DNS setup.

Note

DNS changes can take a while to propagate depending on your provider and TTL. RouteSeam checks automatically every few minutes, so you don’t need to babysit it.

4. Click Check DNS

Back in RouteSeam, click Check DNS. When the record resolves correctly, your domain moves to DNS Verified.

If the check fails, RouteSeam shows what it saw versus what it expected — usually a typo, a record created at the wrong name, or propagation that hasn’t finished yet.

5. TLS provisions automatically

Once DNS is verified, RouteSeam provisions a Let’s Encrypt certificate for your hostname automatically. The status moves through Provisioning SSL to Active. No action is required from you, and renewals are automatic forever after.

6. Test your redirect

Verify the redirect end-to-end with curl:

curl -I https://oldcompany.com

Expected output:

HTTP/2 308
location: https://newcompany.com/

With path and query preservation enabled, deep links carry through:

curl -I "https://oldcompany.com/products/widget?utm_source=google"

HTTP/2 308
location: https://newcompany.com/products/widget?utm_source=google

Tip

Browsers cache permanent redirects aggressively. Test with curl -I rather than your browser to avoid picking up a stale cached redirect from earlier experiments.

Next steps

• Add more domains from the dashboard, or use the API to manage redirects programmatically.
• Monitor traffic on the domain’s analytics view — see analytics.
• Understand the full domain lifecycle, including failure and recovery states.