What Is CDN White-Labeling?
When CDN white-labeling is enabled, image URLs served from the Dyspatch Image CDN use your domain instead of dyspatch.io. This keeps your brand visible in any image path a recipient might inspect.
| Before | After | |
|---|---|---|
| Image URL | https://cdn-web-assets.dyspatch.io/image.png | https://assets-email.yourorg.com/image.png |
Why Use It?
- Brand consistency: Recipients and email clients see your domain in image paths, not Dyspatch's
- Compliance: Some data governance or security policies require assets to appear hosted on company-owned infrastructure
- Deliverability: Serving images from your own domain can improve inbox trust signals for certain senders
How It Works
Dyspatch serves your images through AWS CloudFront. White-labeling works by pointing a subdomain of your choosing to the Dyspatch CDN with a DNS CNAME record. No images are physically moved; the same content is served under your domain.
Setup Process
Setting up CDN white-labeling requires brief coordination between your team and Dyspatch.
Step 1: Request the Feature
Contact your Account Manager or Dyspatch support to request CDN white-labeling for your account. Include:
- The custom domain or subdomain you intend to use (for example,
assets-email.yourorg.com) - Optionally, the name and email of a technical contact who will update your DNS records
Step 2: Add the DNS CNAME Record
Dyspatch will send your technical contact the specific CNAME target value your engineer needs to create the DNS record.
Step 3: Confirm and Activate
Once the DNS record is live, let Dyspatch know. We'll verify the configuration and enable the custom domain on your account.
Step 4: Migrate Existing Assets
After confirming images load correctly from the new domain, Dyspatch will run a migration to update all existing draft and published image URLs in your Dyspatch account to use the new domain.
Start the CDN White-Labeling Process
Contact your Account Manager or support@dyspatch.io to enable CDN white-labeling for your account.