Custom Domains

Publish your changelog on your own subdomain with automatic SSL. For hosted pages, widgets, README badges, and vanity links, see the Sharing guide.

Plan Requirements

Pro includes 3 custom domains; Business includes unlimited domains. Each repository can have one custom domain. Business also removes KittyLog branding on custom domains.

1. Add Your Domain

Open your repository's Sharing tab and add a subdomain such as changelog.example.com. Keep the DNS Configuration details open for the next step.

2. Configure DNS

Copy the CNAME and TXT records shown in DNS Configuration into your DNS provider. Use the verification token generated for your domain.

Example for changelog.example.com

CNAME
changelog.example.com → kittylog.pages.dev
TXT
_kittylog.changelog.example.com → your generated verification token

If your DNS is managed by Cloudflare, set the CNAME to DNS only (gray cloud).

Copy the records from your own DNS Configuration panel. The domain and verification token shown here are examples.

3. Verify DNS & Enable Visibility

Select Verify DNS Configuration. After verification, KittyLog provisions SSL automatically. Keep Custom domain visibility enabled so readers can visit your published changelogs. Drafts stay private.

Hosted URL visibility and Custom domain visibility are separate controls. Turning off one does not turn off the other. These settings control access to the changelog, independently of your GitHub repository's visibility.

Verified confirms your DNS setup. Keep Custom domain visibility enabled so readers can open the link.

Troubleshooting

  • DNS changes can take up to 24–48 hours to propagate. If verification fails, check both record names and values, then retry.
  • If your DNS provider appends the zone name automatically, enter only the host part (for example, changelog or _kittylog.changelog).