How to Serve Your dochost Pages From Your Own Domain

Every page you publish on dochost lives at dochost.co/d/{slug}. On the Max plan you can put those same pages behind a domain you control instead — docs.yourcompany.com/{slug} — so a link you send a client or a class carries your name, not ours. This guide walks through the setup once, with screenshots. The whole thing takes about ten minutes, and most of that is waiting for DNS.

What you need

• A Max subscription. Custom domains are a Max feature; see pricing.
• A domain you own, and access to wherever its DNS is managed (Cloudflare, Namecheap, GoDaddy, Route 53, and so on).
• A subdomain to use. docs.yourcompany.com, share.yourcompany.com, pages.yourcompany.com — any prefix you like. Bare top-level domains (yourcompany.com with no prefix) cannot be connected; if you type one, dochost proposes docs.yourcompany.com and lets you change the prefix.

You can connect up to two domains per account.

Step 1 — Add your domain in dochost

Open Settings → Domains and click Add a domain. Type the subdomain and click Add domain.

The step bar at the top of the card tracks where you are: Add your domain → Create one DNS record → We take it from here. You only do the first two.

Step 2 — Create one CNAME record at your DNS provider

As soon as the domain is added, dochost shows the exact record to create. Pick your DNS provider from the chips and the field labels switch to that provider's wording; the Open … DNS settings button deep-links to the right screen where the provider supports it.

The record is always the same shape:

Use the Copy buttons rather than retyping — a stray space in the target is the most common typo.

On Cloudflare

Cloudflare is the provider most readers use, so here is that path in full. Open your domain, go to DNS → Records, and click Add record.

In the dialog set Type to CNAME, Name to your prefix, and Target to cname.dochost.co. Then turn Proxy status off so it reads DNS only with a grey cloud, and click Save.

Other providers have no proxy toggle, so there is nothing to switch off; just create the CNAME.

Step 3 — We take it from here

Back in dochost the row now shows Verifying. You can close the tab: dochost polls DNS, issues an HTTPS certificate once the record resolves, and emails you the moment the domain goes live — usually within ten minutes. If you would rather watch, Check now runs a check on the spot.

If anything is wrong, the row turns to Needs attention with a one-line reason, and the email says what to fix:

When it is live

Your first custom domain becomes the primary address automatically: every page you publish from now on gets a docs.yourcompany.com/… link, in the dashboard, the success panel, the browser extension and the MCP tools alike.

A few things worth knowing about that screen:

• Every address keeps working. Links you already shared on dochost.co/d/… still resolve, and so does a second domain or a yourname.dochost.co subdomain. Primary only decides which one new links use. Change it with Set as primary at any time.
• Pages themselves do not change. Your documents are still stored once; the domain is just another door to the same page. Passwords, expiry and analytics carry over.
• Removing a domain stops links on that hostname, but the pages stay published and reachable at every other address.
• If you leave Max, your custom domains stop serving and links fall back to dochost.co/d. The setup is kept for 90 days, so re-subscribing brings the domain back without redoing DNS.
• Dialogs say sandbox--{slug}.dochost.co. When a page's own script calls alert() or confirm(), the browser names the per-document sandbox origin, even on your domain. That is by design: each published page runs in its own isolated origin, which is what keeps one page from reading another's data.

Try it

Upgrade to Max, open Settings → Domains, and add the subdomain you want. If the record is right, you will have the email before you finish your coffee.