If a recipient clicks a Sendr page link and sees a "Your connection is not private" or SSL warning in their browser, the most likely cause is a custom domain configuration issue.

If you are using a custom domain

This warning appears when the SSL certificate for your custom domain has not been fully provisioned, or when DNS is not correctly pointing to Sendr.

Check your DNS recordsGo to your domain provider and confirm that the CNAME record for your Sendr subdomain (e.g. pages.yourcompany.com) is correctly pointing to the Sendr destination. An incorrect or missing DNS record will cause SSL to fail.

Wait for DNS propagationIf you recently set up or changed your custom domain, DNS changes can take up to 24 hours to propagate. The SSL certificate is provisioned automatically once DNS is correctly resolved. Wait and check again after 24 hours.

Reconnect the custom domainIf DNS looks correct but the warning persists, try removing and re-adding your custom domain in Settings > Custom Domain to trigger a fresh SSL provisioning attempt.

If you are not using a custom domain

Sendr-hosted pages on the default Sendr domain should not show SSL warnings. If you are seeing this on a non-custom domain page, contact us at [email protected] with the affected page URL.

Was this helpful?