> ## Documentation Index > Fetch the complete documentation index at: https://docs.os.default.com/llms.txt > Use this file to discover all available pages before exploring further. # Domains in Default > Connect your website, install the Pixel, check its DNS record, and manage detected forms in Settings → Domains. **Settings → Domains** brings website tracking and email sending domains together. Admin access is required. * **Website** lists the domains the Default Pixel tracks. * **Email** lists your sending domains. See [Email domains](https://docs.os.default.com/settings/domains/email.md). Old **Signals** and **Settings → Pixel** links redirect here. ## Connect a website Select **Add domain** in the **Website** card. On **Load the pixel from your website**, enter your website address and select **Continue**. The address is suggested from your work email when available. Your website detail page contains everything you need: 1. Under **Add the snippet to your site**, select **Copy**. Paste the complete snippet before the closing `` tag on every page you want tracked. 2. If a CNAME record is shown under **Connect your domain**, add it at your DNS provider. Copy the full **Name** and exact **Points to** value shown. For a website at `www.example.com`, the name is `connect.www.example.com`. If your provider appends the DNS zone `example.com` automatically, enter `connect.www` instead. Keep the website's existing DNS records. 3. If you added a record, select **Check status** after saving it. DNS changes can take up to 48 hours to propagate. If custom hosting is unavailable and no record is provided, skip the DNS steps. The supplied snippet loads from Default's CDN and works without a custom connection. When custom hosting is configured, it loads from a hostname such as `connect.yourdomain.com` and retains the default CDN as a fallback. Use the supplied snippet: it includes your workspace's public key and loader behavior. For an existing website already sending Pixel activity through the default CDN, the page shows **Live** and the custom CNAME is optional. When custom hosting is available, select **Check status** to prepare its connection instructions. If you enable custom hosting, replace the old snippet with the new one shown on the page. For installation details, see [Set up the Pixel and Forms SDK](https://docs.os.default.com/pixel-sdk-setup.md). ## Check connection status A website shows the same status in the **Website** list and on its page: | Status | Meaning | | - | - | | **Live** | Default has received events from the Pixel on this website, or the website has a form in **Forms**. While its custom record is pending or doesn't match, the list adds **Finish DNS setup** or **DNS record doesn't match** beside it, and the Pixel keeps loading from the default CDN. | | **Ready** | Custom hosting is verified, but no Pixel events have arrived yet. Load a page that has the snippet to turn it **Live**. | | **Waiting for DNS** | The CNAME is absent, still propagating, or waiting for hosting verification. | | **Add snippet** | The website has no custom connection and Default hasn't received anything from it yet. | | **Error** | The DNS record does not match, or the website has a stored failure. Correct the record and select **Check again**. | A connected record collapses to **Record connected**. Select **Show** to inspect its values. The **Checked** timestamp records the latest completed DNS check. A temporary lookup failure keeps the saved instructions and shows an error so you can retry. A verified hostname alone does not confirm that the snippet is installed. A saved form can also make the website show **Live** without any Pixel events, so do not use the status alone to confirm installation. Check that the snippet runs on every page you want tracked and verify fresh activity. ## Forms on your site A **Live** or **Ready** website shows detected forms with their page, field count, and last-seen time. Pending detections also appear before the website reaches either status, including sites using the Forms-only snippet. **Show all** expands a longer list; **Open Forms** takes you to the Forms app. * Select **Map N fields** to review a detection or map fields on an existing form. An active form that still needs mapping keeps its switch, so you can turn it off. * After mapping a new detection here, it stays off until you turn it on. * Use the switch to activate a mapped form. Turning an active form off asks you to confirm its impact on connected workflows. You can also add forms from **Forms → Create new → Catalog forms**. See [Your forms](https://docs.os.default.com/forms/your-forms.md). ## Reveal The same websites also list their pages under **Reveal**. Select a path to open it in a new tab. Turn on a page's switch to identify the companies visiting it; the confirm shows what a lookup costs before you select **Enable Reveal**. While a change saves, the switches stay disabled. Turning a page off stops Clearbit Reveal and Demandbase lookups on that page. If Vector is on, a confirmation also explains that turning off the last Reveal path removes Vector's restriction to selected paths and can expand paid coverage to every eligible Pixel page. Turn Vector off under **Settings → Connections** to stop its spending. See [Reveal](https://docs.os.default.com/forms/reveal.md#turn-on-reveal-for-a-page). ## Subdomains are included Adding `acme.com` covers that exact address and its subdomains, including `www.acme.com` and `blog.acme.com`. Add a subdomain separately when you want separate attribution. The most specific connected domain wins: if both `acme.com` and `shop.acme.com` exist, traffic from `shop.acme.com` belongs to that entry. Different domains, such as `acme.com` and `acme.co.uk`, need separate entries. ## Edit or remove a website Select the pencil beside the domain to edit its address. Changing the address removes its old custom hosting connection. Add the new DNS record if one is provided, and replace the snippet on the new website. Under **Danger Zone**, select **Delete Domain**, then confirm with **Delete domain**. This stops new tracking and removes the entry from the list, including any custom pixel hostname. Existing forms and historical data are kept. Add the same domain again to restore it with its pages and forms. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.