Docs

Custom domain

With a custom domain your clients never see our address. They sign in to the client portal and open your status pages on an address of your own, such as monitor.youragency.com.

What you get

One domain for your workspace, on plans that include a custom domain. On it:

  • monitor.youragency.com opens the client portal. The sign-in page carries your logo and name from Settings → Branding.
  • monitor.youragency.com/status/your-name opens each status page of the workspace.
  • Sign-in links and monthly reports that we email to your clients point to your domain.

Your own sign-in and dashboard stay on http://pulsekeeper.io. On your domain only the pages for your clients answer; anything else returns "not found".

More domains, or a status page on a client's own domain (such as status.yourclient.com), are part of a custom plan.

Set it up

  1. Pick a subdomain you control, such as monitor.youragency.com or status.youragency.com. It has to be a subdomain: the bare domain (youragency.com) cannot point to us with a CNAME record.

  2. In PulseKeeper, open Settings → Branding → Your domain, enter the subdomain and click Connect domain.

  3. At the DNS provider of your domain (Cloudflare, your registrar, your hosting panel …), add one record:

    Type Name Target
    CNAME monitor (or the full monitor.youragency.com) –

    Warning: If your DNS is on Cloudflare, set the record to DNS only (grey cloud), not proxied. A proxied record hides our target and the certificate is never issued.

  4. Wait. We check every few minutes. Once the record is visible, the certificate is issued automatically, usually within 15 minutes, and the status changes to Active. You can click Check now to check right away.

You do not need to buy or renew a certificate: we issue and renew it for you as long as the record is in place.

Moving a domain that is already live

If the subdomain already serves something your clients use, add the TXT record shown under Moving a live domain? first, and switch the CNAME only after that. The certificate is then ready before the switch, so nobody sees a certificate error.

When it does not work

  • Still "Waiting for DNS" after an hour. Check the record in a terminal:

    dig CNAME monitor.youragency.com +short

    It should print –. If it prints nothing, the record is not saved or is on the wrong name (some providers add the domain to the name for you, so monitor.youragency.com becomes monitor.youragency.com.youragency.com).

  • A CAA record on your domain can block the certificate. If you have one, allow letsencrypt.org, pki.goog and ssl.com.

  • The message under the record comes from our certificate provider and says what it saw at the last check.

Removing it

Click Remove. The domain stops working right away and your clients use the regular addresses again: the portal at http://pulsekeeper.io/portal and status pages at http://pulsekeeper.io/status/your-name. You can then delete the DNS record. If your plan no longer includes a custom domain, visits to it are forwarded to the same page on our address.