Custom Domains

Connect branded subdomains to status pages via Cloudflare for SaaS.

Custom domains are attached per status page and verified through DNS + Cloudflare Custom Hostnames. Hosted status URLs remain available as fallback.

v1 Domain Rules

Only specific subdomains are supported (for example status.customer.com). Apex/root domains and wildcard domains are rejected by validation.

Setup Flow

Open your status page settings and enter a custom subdomain.
Create DNS CNAME pointing your subdomain to pages.pulsebeacon.io.
Click Verify now.
If Cloudflare requests validation TXT/DCV records, add them exactly and verify again.
Once SSL and hostname status are active, domain becomes live at https://your-domain.

Required DNS Record

Type: CNAME
Name: status.customer.com
Target: pages.pulsebeacon.io

Pending DNS · CNAME is missing or still propagating.

Pending hostname verification · DNS looks correct and activation is in progress.

TXT validation required · add the TXT record(s) shown in PulseBeacon.

Waiting for SSL · validation succeeded and certificate issuance is in progress.

Active · domain is verified and serving HTTPS.

Error · review the status message, correct DNS/validation, then verify again.

Custom domains are available on paid plans.
On downgrade, existing domains are not auto-deleted, but new additions can be blocked.
Domain uniqueness is global across status pages.

If verify repeatedly shows pending DNS, query CNAME publicly and verify exact target.
If TXT/DCV appears, add records exactly as shown in PulseBeacon modal (name + value).
Use verify again after DNS propagation; SSL issuance can take additional time after TXT is valid.
If Cloudflare hostname mapping is stale, disconnect and reconnect the domain from status page settings.