ShipPulse
  • Pricing
  • Docs
  • Blog
  • Compare

Product

TestimonialsChangelogStatus PagesFeedbackRoadmapPricing

Resources

DocsBlogAPI ReferenceSDKHelp Center

Company

AboutContact

Legal

TermsPrivacyCookie PolicyDPASub-processors

Product updates

Changelog updates only. Unsubscribe any time.

ShipPulse operated by Igor Bogdanov, Limassol, Cyprus. [email protected]. Cyprus registration number pending — will be published once issued.

ShipPulse

© 2026 ShipPulse. All rights reserved.

OverviewQuick StartCore ConceptsWidget ReferencePlatform GuidesAPI ReferenceAPI PlaygroundError HandlingPaginationRate LimitingJavaScript SDKWebhooksZapier, n8n & MakeCustom DomainsTeam ManagementBilling & PlansNotification ChannelsAI FeaturesOverviewFrom SenjaFrom Testimonial.toFrom HeadwayFrom Canny

Introduction

  • Overview
  • Quick Start
  • Core Concepts

Embed Widgets

  • Widget Reference
  • Platform Guides

REST API

  • API Reference
  • API Playground
  • Error Handling
  • Pagination
  • Rate Limiting

SDK & Webhooks

  • JavaScript SDK
  • Webhooks
  • Zapier, n8n & Make

Guides

  • Custom Domains
  • Team Management
  • Billing & Plans
  • Notification Channels
  • AI Features

Migrations

  • Overview
  • From Senja
  • From Testimonial.to
  • From Headway
  • From Canny

Need help?

[email protected]
Configuration

Custom Domains

Serve your changelog, status page, and Wall of Love from your own domain (e.g. status.yourapp.com) instead of the default shippulse.dev/status/your-project. Available on Pro and Agency plans.

Supported on these public pages:

Status Page

status.yourapp.com

Changelog

updates.yourapp.com

Wall of Love

reviews.yourapp.com

Setup steps

1

Choose a subdomain

Pick a subdomain for your public page, e.g. status.yourapp.com, updates.yourapp.com, or reviews.yourapp.com. Root domains (without a subdomain) are not supported — use a www or named subdomain.

2

Add the CNAME record

In your DNS provider (Cloudflare, Route 53, Namecheap, etc.), create a CNAME record pointing your chosen subdomain to cname.shippulse.dev.

3

Enter the domain in ShipPulse

In your project dashboard → Settings → Custom Domain, enter the full subdomain (e.g. status.yourapp.com) and click Save.

4

Wait for DNS propagation

DNS changes can take 1–48 hours to propagate globally, but usually resolve within a few minutes. ShipPulse automatically provisions an SSL certificate via Let's Encrypt once the CNAME is detected.

DNS record example

Add this CNAME record in your DNS provider:

TypeNameValueTTL
CNAMEstatuscname.shippulse.devAuto / 300

Verify with dig

bash
# Check CNAME is set correctly
dig CNAME status.yourapp.com +short
# Expected: cname.shippulse.dev.

# Check SSL certificate
curl -I https://status.yourapp.com

SSL / HTTPS

ShipPulse automatically provisions a TLS certificate via Let's Encrypt once your CNAME is verified. Certificate provisioning takes 1–5 minutes. Certificates auto-renew before expiry — no action needed on your part.

Cloudflare proxy note

If your domain is on Cloudflare, set the DNS record to DNS only (grey cloud), not Proxied (orange cloud). SSL termination is handled by ShipPulse — Cloudflare proxying will break certificate provisioning.

Troubleshooting

Domain shows 'Not verified'

Check your CNAME record is set to cname.shippulse.dev (not shippulse.dev). Use dig or nslookup to verify: dig CNAME status.yourapp.com.

SSL certificate not provisioning

Ensure Cloudflare proxy (orange cloud) is disabled — set DNS-only mode. The CNAME must point directly to ShipPulse, not through a Cloudflare proxy.

Browser shows certificate error

SSL provisioning takes 1–5 minutes after CNAME verification. Clear your browser cache and try again. If it persists after 30 minutes, contact support.

Custom domain shows wrong project

Each domain can only be assigned to one project. Check that the domain isn't already set on another project in your account.

Still stuck? Contact support with your domain and we'll investigate.