White-Label Custom Domains: Host HTMLVault Links on Your Own Domain

The Problem with Generic Link Domains

When you send a prospect a link to a proposal or pricing dashboard, the domain matters. A URL like htmlvault.dev/abc123 works, but it raises questions: What is this service? Is it safe to click? Should I whitelist it in our email security?

For sales teams sending high-value proposals, that moment of hesitation costs you. For marketing teams running campaigns, generic domains get flagged by corporate email filters more often than your own domain does. And for RevOps leaders building repeatable processes, inconsistent branding across touchpoints erodes the professional image you've worked to build.

White-label custom domains solve this by letting you host HTMLVault links on a domain you control. Your prospects see proposals.acme.com/deck-q4 instead of a third-party URL. Same security, same analytics, same HTMLVault infrastructure—but wearing your brand.

Who This Is For

Pro users get a branded subdomain on HTMLVault's infrastructure: yourteam.htmlvault.dev. This is ideal for small teams who want better branding without managing DNS records.

Enterprise users get full custom domain support: reports.yourcompany.com or any subdomain you control. You point a CNAME record to HTMLVault, and SSL certificates and routing are handled automatically.

The users who benefit most:

• Sales reps sending proposals and one-pagers to prospects who've never heard of HTMLVault
• Marketing teams distributing landing pages and campaign assets via email
• RevOps leads building standardized link-sharing workflows that need to look consistent
• IT and security teams who prefer traffic to flow through domains they recognize in logs

How to Enable Custom Domains

Pro: Claiming Your Subdomain

Pro users can claim a subdomain like acme.htmlvault.dev directly from the dashboard. No DNS configuration required—HTMLVault hosts it for you.

1. Go to Settings → Domains
2. Enter your desired subdomain (letters, numbers, and hyphens only)
3. Click Claim Subdomain
4. Your links now have the option to use this domain

Subdomain availability is first-come, first-served. Once claimed, it's yours as long as your Pro subscription remains active.

Enterprise: Connecting Your Own Domain

Enterprise users can connect any subdomain they control. Setup requires adding one CNAME record in your DNS provider—no ongoing maintenance after that.

1. Go to Settings → Domains
2. Enter your desired domain (e.g., reports.yourcompany.com)
3. HTMLVault generates a CNAME target (e.g., cname.htmlvault.dev)
4. Add this CNAME record in your DNS provider (Cloudflare, Route 53, GoDaddy, etc.)
5. Return to HTMLVault and click Verify Domain
6. HTMLVault automatically provisions and renews your SSL certificate

DNS propagation typically takes 5–30 minutes, though some providers may take up to 24 hours. You can confirm the record is live by running dig CNAME reports.yourcompany.com from your terminal.

Worked Example: A Sales Team's Proposal Domain

Imagine you're the RevOps lead at a B2B software company. Your sales team sends 50+ proposals per month using HTMLVault. Currently, links look like htmlvault.dev/p/abc123.

You upgrade to Enterprise and configure proposals.acme.com as a custom domain. After adding the CNAME record in your company's Cloudflare account and verifying in HTMLVault, your team's links now look like:

proposals.acme.com/enterprise-q4-pricing

When prospects receive these links in email, their security filters recognize acme.com as a known sender domain—fewer emails land in spam. When prospects click through, they see your domain in the browser bar, reinforcing that this is official company material.

Everything else works identically. You still see views, scroll depth, time-on-page, geographic data, and channel attribution in analytics. Password protection and auto-expiry still apply. PII scanning still runs before publish. The only thing that changes is the domain your prospects see.

Impact on Email Deliverability

Email security systems evaluate links based on domain reputation. When you send emails containing links to your own domain, those links inherit the trust you've built through SPF, DKIM, and DMARC records on your root domain.

Links to third-party domains—even legitimate ones—often receive additional scrutiny in enterprise email environments running tools like Proofpoint, Mimecast, or Microsoft Defender. Custom domains reduce this friction without requiring any changes to your email infrastructure.

Limits and Caveats

• Pro subdomains must be unique across all HTMLVault users. Common names may already be taken.
• Enterprise custom domains must be subdomains (e.g., links.yourcompany.com), not root domains. This is a technical requirement of how CNAME records work.
• SSL certificates are provisioned automatically. If your domain has CAA records restricting which certificate authorities are allowed, add Let's Encrypt to that list before verifying.
• One domain per workspace on Pro. Enterprise customers can configure multiple domains for different teams or use cases.
• If your subscription lapses, links on custom domains will stop resolving after a 30-day grace period.

Why This Matters

Custom domains aren't about vanity—they're about removing friction from workflows that already exist. The sales rep sending a six-figure proposal shouldn't have to explain what htmlvault.dev is. The marketing team running an email campaign shouldn't lose opens to spam filters. The RevOps lead standardizing link-sharing across the org shouldn't have to compromise on brand consistency to get security scanning and engagement analytics.

White-label domains give each of those people HTMLVault's full feature set—access controls, PII scanning, configurable expiry, scroll depth and time-on-page analytics—while keeping their brand front and center. Prospects see a familiar domain. IT sees recognizable traffic in their logs. And the team still gets the engagement visibility that makes sharing HTML worth doing in the first place.