> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a subdomain

> Register a subdomain, add two DNS records, and wait for allGood to verify it and issue an SSL certificate.

A connected subdomain is the address allGood uses to host your landing pages, receive form submissions, record tracking events, and serve the links in your emails. Without one, the tracking tag has nowhere to load from, forms have no endpoint, and pages have nowhere to live.

This article walks you through registering a subdomain on **Web Edge Sessions** and adding the DNS records that prove you own it. For why each step exists, see [How Web Edge keeps your domain secure](https://docs.allgoodhq.com/mk/settings/web-edge/how-it-works.md).

## Before you start

* You have the **Admin** or **Power user** role, and you can open **Web Edge Sessions** in your account settings. With the **Standard** role, you cannot register, sync, delete, or change the default subdomain.
* You have access to your DNS provider, or a teammate who does.
* You have chosen a subdomain, such as `pages.yourbrand.com` or `mk.yourbrand.com`.

**Choose a subdomain that nothing else uses.** Pointing a hostname at allGood takes it over completely. It will serve allGood pages, not your current site. If you are migrating from Marketo or HubSpot, do not register the subdomain that platform uses today. Keep it free so you can redirect old links when you cut over.

Registering a subdomain does not touch your main website. Adding `pages.yourbrand.com` has no effect on `www.yourbrand.com`.

## Register the subdomain

**1. Register the hostname**

In **Add a subdomain**, enter the full hostname in **Hostname**, for example `pages.yourbrand.com`. Do not enter only `pages` or only `yourbrand.com`. Select **Register**.

![The Add a subdomain card, where you register the hostname](https://mintcdn.com/allgoodtechnologyinc/bf1LRHwyriZvgDxT/images/mk/web-edge/setup-web-edge-add-subdomain.png?fit=max\&auto=format\&n=bf1LRHwyriZvgDxT\&q=85\&s=c85f1e5af37d32bb5b9fe4bda6ff8c14)

The Add a subdomain card, where you register the hostname.

**2. Open the DNS instructions**

On the new row, open the **⋮** menu and choose **DNS setup instructions**. A drawer lists every record you need. Each has a copy button and a tick that shows whether it has resolved yet.

**3. Add the routing record at your DNS provider**

A **CNAME record** is a DNS instruction that points one address at another. Add a CNAME on your subdomain, for example `pages.yourbrand.com`, with the target shown on the row. It sends visitors on your subdomain to **allGood Edge**, the network that hosts and serves your pages.

**4. Add the certificate record**

The second record lets allGood issue an SSL certificate for your subdomain. The drawer shows one of two shapes:

* **A delegation CNAME** on `_acme-challenge.` plus your subdomain. Add it once, and the certificate renews automatically from then on. Copy the unusual prefix exactly as shown.
* **TXT records** at the same `_acme-challenge.` name. There may be more than one. Add every record shown. If you miss one, a backup certificate authority can fail to renew later without any warning.

The values in the drawer are unique to your subdomain. Always copy them from the drawer. Do not reuse values from this article or from another subdomain.

**5. Wait, then select Sync**

DNS can take a few minutes to an hour to propagate. Back on **Web Edge Sessions**, select **Sync** to re-check your records. The list refreshes about 30 seconds later.

![The domain table, showing the four-step progress rail and the default domain badge](https://mintcdn.com/allgoodtechnologyinc/bSgN7e8oktmf793O/images/mk/web-edge/setup-web-edge-domain-table.png?fit=max\&auto=format\&n=bSgN7e8oktmf793O\&q=85\&s=72acae05b66044d5eb02474fcc648810)

The domain table, showing the four-step progress rail and the default domain badge.

**6. Confirm every record is verified**

Reopen the DNS drawer. When both records resolve, each shows a green tick and the drawer confirms the domain is live.

![The DNS drawer once every record has resolved and the domain is live](https://mintcdn.com/allgoodtechnologyinc/bf1LRHwyriZvgDxT/images/mk/web-edge/setup-web-edge-dns-drawer-verified.png?fit=max\&auto=format\&n=bf1LRHwyriZvgDxT\&q=85\&s=ffe6d3741fdfe3bb75ea2eff85775f6c)

The DNS drawer once every record has resolved and the domain is live.

> [!WARNING]
>
> Many DNS providers, including AWS Route 53, treat the Host or Name field as relative to your domain. Pasting the full name can create a doubled record such as `_acme-challenge.pages.yourbrand.com.yourbrand.com`, and the record fails with no error. Enter the host without your domain suffix, for example `_acme-challenge.pages`, or add a trailing dot if your provider supports it. This is the most common setup failure.

When the row's **State** reads **active** and all four steps under **Progress** are done, allGood has issued your SSL certificate and provisioned bot protection. You can now publish landing pages and forms on that subdomain.

## What the four progress steps mean

| Step | Means |
| - | - |
| **Hostname created** | allGood has registered your subdomain. |
| **DNS propagated** | allGood can see your routing record. |
| **SSL active** | The certificate is issued and deployed. |
| **Bot protection ready** | The bot-check widget covers this subdomain. |

The row's **State** badge starts at **propagating** and moves to **active** once DNS is verified. Only **active** counts as connected.

> [!NOTE]
>
> Bot protection finishes last, because a widget can only cover a subdomain once its certificate is live. If a row shows **SSL active** but not **Bot protection ready**, select **Sync** again. Until it is ready, forms that require a bot check cannot be registered on that subdomain.

If a subdomain has sat in **propagating** for more than an hour or two, treat it as broken, not slow. Compare every record against the DNS drawer and look for the doubled name described above. The [Web Edge FAQ](https://docs.allgoodhq.com/mk/settings/web-edge/faq.md) covers DNS caching, Cloudflare proxying, and how to check records yourself.

## Manage more than one subdomain

If you connect more than one subdomain, one of them is the **default**. allGood fills it into every snippet and URL it generates, such as your tracking tag, the Google Tag Manager template, form endpoint URLs, and published page URLs. Only an active subdomain can be the default, and there is always exactly one.

Open the row's **⋮** menu to change it or to remove a subdomain you no longer need.

![The row actions menu, with DNS setup instructions, Set as default and Delete domain](https://mintcdn.com/allgoodtechnologyinc/bf1LRHwyriZvgDxT/images/mk/web-edge/setup-web-edge-domain-actions.png?fit=max\&auto=format\&n=bf1LRHwyriZvgDxT\&q=85\&s=15bf03bdb2a4b291c71352822e4d1721)

The row actions menu, with DNS setup instructions, Set as default and Delete domain.

* **Set as default** changes what allGood generates from now on. Pages already published and tags already installed keep working.
* **Delete domain** asks you to type the hostname, then immediately stops landing pages, form capture, and tracking on that subdomain. You cannot delete the default. Make another subdomain the default first.

allGood also serves a preview address, shaped like `{yourTenantId}.preview.allgoodmk.app`, for signed page previews and the hosted test page. It is not branded and is not where real traffic goes, so it does not replace a connected subdomain.

## Next steps

After the subdomain is active, [list the websites allowed to send data](https://docs.allgoodhq.com/mk/settings/web-edge/allowed-origins.md).

## Related articles

* [How Web Edge keeps your domain secure](https://docs.allgoodhq.com/mk/settings/web-edge/how-it-works.md)
* [Allowed origins](https://docs.allgoodhq.com/mk/settings/web-edge/allowed-origins.md)
* [Saved vs live at the edge](https://docs.allgoodhq.com/mk/settings/web-edge/edge-sync.md)
* [Web Edge FAQ](https://docs.allgoodhq.com/mk/settings/web-edge/faq.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.