SignatureCat SignatureCat Docs
Status Help Open app

Serve images from your own domain

By default, logos and banners in your signatures are served from images.signature.cat. You can serve them from a subdomain of your own domain instead - for example images.yourcompany.com. Mail clients fetch images from the sender's own domain more readily, so deliverability improves, and the URLs carry your brand.

Setup breaks nothing: until the domain is active, images keep loading from images.signature.cat, and after activation the switch happens automatically for newly rendered signatures. Templates stay unchanged.

Requirements

  • An Admin access level in SignatureCat.
  • Access to your domain's DNS settings.
  • A subdomain (like images.yourcompany.com). Apex domains (yourcompany.com) are not supported by design.

Set it up

  1. Open the image library from any template editor on Signatures (Logo or Banner button) and choose Use your own domain in the serving bar.
  2. Enter a subdomain - for example images.yourcompany.com - and click Generate DNS record.
  3. Add one DNS record at your DNS provider, exactly as shown: a CNAME pointing your subdomain to cdn.signature.cat. That single record is all SignatureCat needs. Some providers want only the part before your domain in the Name field, and the wizard prints that short form for you.
  4. Wait for verification. SignatureCat checks the record automatically every few minutes; you can also click Check now. Activation usually takes a few minutes, sometimes up to an hour while DNS refreshes. The TLS certificate is issued for you.

The wizard shows one of three statuses: Waiting for DNS records, Domain active or Verification failed.

Once active: "New emails fetch images from your domain. Templates stay unchanged - the switch happens automatically."

Verification not going through?

If the domain stays pending after a check, or verification fails, the wizard reveals a TXT record under the heading Verification not going through?. It is a fallback for two rare cases: a CAA record on your domain blocks the certificate authority SignatureCat uses, or the hostname is already proxied through another Cloudflare zone. Add the TXT record alongside the CNAME, then click Check now again. In every other case the CNAME on its own is enough.

Removing the domain

Removing the domain in the wizard switches image serving back to images.signature.cat automatically for new emails. Nothing breaks.

Active domains are re-checked automatically, so a CNAME that disappears is noticed within about a day: the domain drops out of the active state and newly rendered signatures fall back to images.signature.cat on their own. That is a safety net for future signatures, not a repair for the ones already in recipients' inboxes - hence the order above.