Build

Someone on your team wants to publish pages on your domain. Here's what that takes.

Coframe hosts the pages. You add one or two DNS records. Nothing on your current site changes, and Coframe issues the certificates.

Three options
Question	Example	What you add	Good for
Subdomain	`go.yourbrand.com`	One `CNAME` to `pages.cofra.me`	Most teams. Independent of your main site.
Root domain	`yourbrand.com`	An `ALIAS`/`ANAME` at the root (or a flattened `CNAME`) plus a `CNAME` for `www`	A domain bought for one campaign or product. Coframe serves the whole domain.
Subfolder	`www.yourbrand.com/lp/`	A proxy or rewrite rule on the platform that serves your site	Sharing your root domain's search authority.

The two-step setup

Step 1: Verify and issue the certificate first. The Domains panel lists a TXT record and an _acme-challenge CNAME. These don't change where the domain points, so nothing goes down. The panel re-checks every 30 seconds.
Step 2: Then point the domain at Coframe. Add the CNAME (or the root ALIAS). The certificate already exists, so the switch has no downtime.

The exact names and values are in the panel, and the marketer can send you a link that shows them. That link needs no login.

Cloudflare: set the records to DNS only (gray cloud).
CAA records: if your domain has them, allow letsencrypt.org, pki.goog and ssl.com.
Root domains: plain CNAME records aren't allowed at the root. Use your provider's ALIAS/ANAME, or serve the site on www and forward the root. Route 53, GoDaddy and Google Cloud DNS don't support alias records to outside hosts.
Never copy IP addresses into A records. They change.

Coframe is SOC 2 Type II.
Pages are served from a global edge network with automatic HTTPS.
Your DNS stays with you. Removing the record removes the pages from your domain.
Nothing is installed on your main site unless you choose the subfolder option.