Skip to main content

Set up a Custom Domain for Your Pages

Written by Harneet Kaur

Plan: Premium, Enterprise
​Platform: All platforms
​Applies to: Tracking, Returns, Protection, and Warranty pages

Overview

A custom domain serves your AfterShip Tracking, Returns, Protection, and Warranty pages from your own address, such as track.yourbrand.com, instead of the default AfterShip domain.

Learn how to set up a custom domain for your pages using AfterShip. This guide walks you through creating a CNAME record with your DNS provider, adding the domain in AfterShip, confirming verification, and switching your links over. Once live, your pages are easier to find, and shoppers stay on your brand from the email all the way to the page.

Before you begin

Requirements

  • A domain you own. If you don’t have one, register one with a domain registrar such as GoDaddy, Domain.com, or Bluehost.

  • Access to that domain’s DNS settings. If someone else manages your DNS, send them the values in Step 1.

Permissions

  • Access to Branded pages > URLs and embedding > Custom domains in AfterShip.

Limitations

  • Your domain works only over HTTPS. AfterShip issues the SSL certificate automatically once the CNAME record verifies.

Step 1: Create a CNAME record with your DNS provider

Point your subdomain to AfterShip so AfterShip can verify the domain and issue its SSL certificate. The record is the same at every provider; only the menu path differs.

  1. Open the DNS settings for your domain at your DNS provider.

  2. Add a CNAME record using the values in the table below.

  3. If your provider offers a proxy option, set Proxy status to DNS only.

Field

Value

Type

CNAME

Host / Name

Your subdomain, for example track or returns

Points to / Target / Value

domains.aftership.com

TTL

Leave unchanged

Proxy status (Cloudflare and similar)

DNS only, not proxied

Find the DNS settings at common providers

Provider

Menu path

GoDaddy

My accounts > Domains > select your domain > Domain Settings > Additional Settings > Manage DNS > Add a new record > Type: CNAME

Cloudflare

Select your website > select the domain from the drop-down at the top left > DNS tab > Add record > Type: CNAME. Set Proxy status to DNS only (grey cloud).

Namecheap

Domain List > Manage next to your domain > Advanced DNS > Add New Record > CNAME Record

Hostinger

DNS Zone Editor > scroll to the CNAME section > Add new

Bluehost

Domains > Zone Editor > select the domain from the drop-down > Add DNS Record

HostGator

cPanel > Domains > Zone Editor > select the domain > CNAME Record

  • Bluehost has two interfaces (Legacy and Rock). The setting is in the same place in both, but the name may differ slightly.

  • If your provider isn’t listed, look for “DNS management”, “DNS zone”, or “Advanced DNS” in its control panel. Every provider supports CNAME records.

  • CNAME changes can take up to 72 hours to propagate, but they usually take effect much sooner.

Important: Set the record to DNS only, the step most people miss. A proxied record resolves, but AfterShip can’t verify it or issue the certificate, and you see Unable to verify domain.

Step 2: Add the domain in AfterShip

Add your domain and choose which products it serves. One domain can serve all four products, each on its own path.

  1. Go to Branded pages > URLs and embedding and open the Domains and page URLs tab.

  2. Under Custom domains, click Add custom domain.

  3. Enter your domain name, for example track.yourbrand.com.

  4. Under Make domain available for, select the products this domain serves: Tracking, Returns, Protection, Warranty. You can select all of them.

  5. Click Add.

The Domains section with the default domain and Add custom domain


​

The Add custom domain dialog

Note: Verification right after you create the record usually fails because DNS hasn’t propagated yet. Wait and retry before you change anything.

Step 3: Confirm verification and set the redirect destination

AfterShip shows a Verifying CNAME record badge on the domain’s row until it can see the record. Once verified, the badge clears and the row lists the domain’s URL for each product, ready to copy.

  1. Wait until the Verifying CNAME record badge clears on the domain’s row.

  2. Click {…} on the domain’s row.

  3. Click Redirect destination to choose whether https://track.yourbrand.com/ opens the Tracking page or the Returns page.

From the same {…} menu, you can also:

  • Click Edit to change which products the domain is available for.

  • Click Delete to remove the domain.

Step 4: Switch your links to the new domain

Test the new domain, then move your shopper-facing links to it.

  1. Open each page on the new domain and confirm it renders on desktop and on a phone.

  2. Update your notification emails, SMS, and storefront links to the new URL.

  3. Keep the old URL working. Shoppers keep old emails, and they click links in them months later.

To stop using the domain, click {…} on its row and click Delete.

Warning: Treat the DNS record as permanent once you’re live. If you change or remove the CNAME record, the certificate can’t renew, and shoppers see a browser security warning.

What your users will experience

After completing these steps:

  • Shoppers open your pages on your own domain over a secure HTTPS connection, with the padlock in the address bar.

  • Shoppers who open the blank path (/) on your domain land on the Tracking page or the Returns page, based on the redirect destination you chose.

  • Shoppers reach every other product through its own path on the same domain.

  • Shoppers with old {short_name}.returnscenter.com links from AfterShip Classic still reach your returns page, so existing links don’t break.

  • You see each product’s URL on the domain’s row in Custom domains, ready to copy.

A custom domain replaces the host only. The product paths stay the same:

Product

Default URL

Custom domain URL

Tracking

https://{short_name}.aftership.com/ or /tracking

https://track.yourbrand.com/ or /tracking

Returns

https://{short_name}.aftership.com/returns

https://track.yourbrand.com/returns

Protection

https://{short_name}.aftership.com/protection

https://track.yourbrand.com/protection

Warranty

https://{short_name}.aftership.com/warranty/{page_name}

https://track.yourbrand.com/warranty/{page_name}

{short_name} is your organization’s short name, which you set in Organization settings.

Troubleshooting

If a page on your custom domain doesn’t load or the domain won’t verify, work through these rows in order.

Problem

Cause

Solution

The Custom domains section shows a notice that custom domains aren’t available

Custom domains aren’t enabled for your account

Contact support before you change anything in DNS.

The domain won’t verify

The record values are incorrect

Set Host to the subdomain only (not the full domain repeated) and the target to exactly domains.aftership.com, with no trailing characters.

The domain still shows Verifying CNAME record

DNS hasn’t propagated yet; changes can take up to 72 hours

Wait, and use a tool such as WhatsMyDNS to check whether the record has propagated.

Unable to verify domain appears while the CNAME resolves

A CDN or proxy service, such as Cloudflare, proxies the record

Switch the record to DNS only and retry verification.

We can’t verify your domain due to bot protection. appears

Your DNS or CDN provider blocks automated checks

Open the page in your browser to confirm it loads. The message is a warning, not a failure.

The domain doesn’t work after you add the CNAME record

An existing A or CNAME record on the same subdomain takes priority over the new one

Remove the conflicting record.

The browser reports a certificate problem

The CNAME record changed or no longer exists

Check that the CNAME record is in place and unchanged, then wait for the certificate to re-issue.

A domain moved to another AfterShip account doesn’t work yet

The switch between accounts isn’t instant when DNS stays the same

Allow the usual propagation time of up to 72 hours.

FAQs

1. Can one custom domain serve every product?

Yes. Make the domain available for Tracking, Returns, Protection, and Warranty at the same time. Shoppers reach each product through its own path, for example returns.yourbrand.com/returns and returns.yourbrand.com/warranty/{page_name}.

2. Can I use a different domain for each product?

Yes. Add another custom domain and make it available for only that product.

3. Why doesn’t my default page URL match my store name?

AfterShip builds the default domain from your organization’s short name, not your store name. Update the organization name and short name in Organization settings (the organization menu at the top right > Manage organization > Organization settings > Basic information), or add a custom domain so the default URL no longer matters.

The Basic information section in Organization settings

4. Do I need to buy an SSL certificate for my custom domain?

No. AfterShip provides the SSL certificate for every verified custom domain and activates it automatically once the CNAME record verifies. You don’t buy or upload anything, but the domain doesn’t work without the certificate.

5. Why should my pages use HTTPS?

HTTPS gives shoppers a secure connection and the padlock in the address bar:

  • Protects data: HTTPS encrypts everything between the shopper and the page.

  • Builds trust: Shoppers are more likely to return to a site that shows as secure.

  • Secures the experience: The whole tracking or returns flow runs on an HTTPS site.

  • Helps SEO: The padlock is a trust indicator, and search engines favor HTTPS.

6. Does the SSL certificate renew automatically?

Yes. AfterShip renews the certificate automatically. If you change or remove the CNAME record, the certificate can’t renew, and shoppers see a browser security warning.

Key takeaways

  • A custom domain serves your Tracking, Returns, Protection, and Warranty pages from your own address

  • Make domain available for sets which products the domain serves, each on its own path

  • One domain can serve all four products, or you can add a separate domain per product

  • Shoppers see your pages on your domain over HTTPS, with SSL issued automatically

  • A proxied CNAME record blocks verification and set it to DNS only

Did this answer your question?