SendGrid "Link Branding" Custom SSL with Nginx

Hey Everyone,

There’s this problem I ran into, and can’t figure out how to solve it.

I signed up for SendGrid and got my domain authorized/verified and also enabled “Link Branding”. Now according to SendGrid, I added their CNAME(s) to my domain’s DNS manager. -> -> … … …

I am running a Node.js app which is now able to send mails through SendGrid and it runs flawlessly but I can’t open the links that are provided in the mail. (It shows the connection to this site is not secure, also the SSL certificate on that URL is not verified).

The server that I am using for this project won’t open any HTTP link, it redirects all HTTP traffic to HTTPS. (This can be a possible reason for the problem I’m facing).

Also, I tried to set CNAME(s) like: -> @ (pointing to A record for

and then using Nginx to forward the url123 traffic to, but that too wasn’t working because I already have a CNAME(www) pointing to @ (A record of

P.S. Adding SSL is also not an option due to the above CNAME conflict.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi there @bhupenpal,

I don’t think that this would work that way. As when you add the CNAME records, they need to be pointed to the SendGrid domain name, this is how they verify the records.

And as the CNAME records are pointing to SendGrid, this means that the traffic for those subdomains would never reach your server as they will route to SendGrid directly.

Here is a step by step video on how to set that up:

I believe that the main reason why they make you point your branded domain to their own site is so that you could still use their analytics features.

Regards, Bobby