DOCUMENTATION

Custom Domains

Last updated May 2026
Publishing
Pro and above

Connect your own domain to a BlnkSpace site so your published pages are served from yourdomain.com instead of yoursite.blnkspace.app. SSL is provisioned automatically. DNS verification is handled via the Vercel infrastructure that BlnkSpace runs on.

Custom domains require a paid plan. Your subdomain on blnkspace.app is available on all plans and does not require DNS configuration.

Before you start

  • You must have a subdomain set up first — custom domains attach to an existing site. Go to Page Settings → Domains to create one if you haven't.
  • You need access to your domain registrar's DNS settings (Cloudflare, Namecheap, GoDaddy, etc.).
  • DNS changes can take up to 48 hours to propagate globally, though they typically resolve within a few minutes on most registrars.

Adding a custom domain

1
Open Page Settings → Domains

Click the settings icon in the document toolbar. In the Domains section, your existing site card is shown, with a "Custom domain" field below it.

2
Enter your domain and connect

Type your domain name (e.g. mysite.com or docs.mysite.com) into the input field, then click Connect. Both root domains and subdomains are supported. The domain is normalized automatically — no need to include https://.

3
Get your DNS records

After connecting, BlnkSpace shows the DNS records you need to add. The record type depends on whether you're using a root domain or a subdomain.

4
Add the DNS records

Go to your registrar's DNS settings and add the records exactly as shown. See the DNS records section below for what to expect.

5
Verify

Come back to the Domains section and click Verify. BlnkSpace polls Vercel's domain verification API and updates the status. Once verified, your domain is live with SSL.

DNS records

The exact records you need depend on whether you're pointing a root domain (like mysite.com) or a subdomain (like docs.mysite.com) at BlnkSpace.

Subdomain (recommended)

For a subdomain like docs.mysite.com, add a CNAME record:

DNS record — subdomain
TypeNameValue
CNAMEdocscname.vercel-dns.com

Root domain

For a root domain like mysite.com, use an A record pointing to Vercel's IP address. Some registrars also support ALIAS or ANAME records as an alternative to A records for root domains.

DNS record — root domain
TypeNameValue
A@76.76.21.21
Vercel may issue project-specific optimized DNS values that differ from the examples above. Always use the exact records shown in your Page Settings panel — the values shown there are fetched live from Vercel for your specific domain.

Verification status

After adding DNS records, the domain card in Page Settings shows one of these states:

StatusMeaning
Pending DNSDNS records have been submitted but verification hasn't completed yet. Click "Verify" to poll for updates.
LiveDomain is verified. SSL is provisioned and traffic is routing correctly.

There's no separate "misconfigured" status shown in the UI — an unverified domain always shows as Pending DNS, whether the records simply haven't propagated yet or don't match what Vercel expects. If the domain is stuck pending after 30+ minutes, double-check the records match exactly what's shown in your Page Settings panel, then click Verify again. Most propagation completes within 5–15 minutes on modern registrars like Cloudflare.

Canonical URL enforcement

Once a custom domain is verified, it becomes the canonical URL for your site. The blnkspace.app subdomain still works but all metadata (Open Graph, sitemap, canonical tags) will reference your custom domain. This prevents duplicate content issues in search engines.

Removing a custom domain

Page Settings → Domains → Remove
Click the Remove button on the custom domain row in the site card. The domain is detached from Vercel immediately and your blnkspace.app subdomain becomes the primary URL again.

After removing, delete the DNS records from your registrar as well — they will no longer point to BlnkSpace but leaving them won't cause harm.

Plan limits and downgrade

Custom domain availability depends on your plan. If you downgrade to a plan with a lower or zero custom domain allowance, excess domains are disconnected automatically as soon as the downgrade takes effect — your oldest connected domains (up to your new plan's limit) are kept, and the most recently added ones are removed first. Your subdomain remains active.

This disconnection happens immediately and silently — there is no advance warning or notification before it happens. If you're planning a downgrade and have more custom domains than your new plan allows, reconnect the domains you want to keep (which resets their "recently added" order) or remove the ones you don't need beforehand.