How to create branded links that include Https:// (SSL) encryption
We include the ability to encrypt all the Https:// traffic from your domain name with an SSL certificate in all of our plans. When you create branded links using Https protocol, the traffic to your content will automatically be encrypted.
Why is Https:// (SSL) important?
SSL is the standard security technology for establishing an encrypted link between a web server and a browser. This link ensures that all data passed between the web server and browsers remain private and integral. To be able to create an SSL connection a web server requires an SSL Certificate.
How do I setup SSL?
We've taken care of all of the setup for you- so there's no extra configuration required on your end. Every link shared with Https:// will be encrypted from now on. What's more- links copied to your clipboard will automatically include Https://.
Rebrandly provides the SSL certificate for all subscribers. If you would like to use your own SSL certificate you'll need to contact us for custom setup and pricing.
This article is about:
- SSL for branded links
- How to share branded links using Https://
- Enabling Https:// for branded domains
- Vanity URL SSL
- Short URLs with https
- SSL Certificate
- Include Https:// in the Branded Links you Copy and Share
- Optimize Your DNS Configuration for Branded Domains Managed by CloudFlare
If i have my own SSL certificate set up in my server through my cPanel, am i able to share https rebrandly links in a subdomain level? (For example: click.mydomainname.com)
And, to do that, do i have to upgrade to a paid plan?
The SSL certificate must be installed on the servers which handle the user requests/clicks with https. If you use your domain or subdomain with Rebrandly via DNS configuration, all the http/https requests will arrive directly to Rebrandly servers, so it is necessary that Rebrandly (and not third-party servers like servers of your hosting provider for example) handles your certificate.
Yes, an upgrade is necessary, because any pre-existing SSL certificate cannot be automatically installed on Rebrandly servers.
Available if you need more help, you can reach us at email@example.com for specific inquiries on your domains
In order to use custom SSL certificate, I need to upgrade to a paid plan. Can it be on any one of the paid plans? Or is i has to be a specific one?
When turning on SSL in settings, the rebrandly.com SSL is not trusted on my Mac (have not tested in browsers on Windows yet). Is there something I am doing wrong? Is this a paid option? I will pay if I knew that was the problem. Thanks.
Rebrandly initiate a request to get an SSL certificate for all branded domains, no matter the plan you have. Sometimes the request takes longer, there are few reasons why it happens:
- your DNS changes are not yet visible worldwide and the Certification Authority cannot confirm/verify that the domain is pointing to Rebrandly
- or, your DNS configuration is somewhat wrong, we are aware of issues with misconfigured AAAA or CAA records.
It appears to us that both of your branded domains are properly configured with an SSL certificate.
You can check for that anytime in tools like this one here https://www.sslshopper.com/ssl-checker.html.
One of the two domains has been added recently (today), so this might be the reason you are contacting, as you tested the https redirection "too early" and the certificate was not there yet. Can you please test it again now, possibly in Incognito mode to reset your browser's caching behaviors?
When I turned on SSL in settings for my custom domain, a orange link appear below "ssl certificate not active"
It has been almost 24 hours past but still it is not activated. When I try shortened any link the page redirect to warning page says page not save to load. Is it because I'm using free plan?
Hello! I have included a new domain (comeu.org) more than a week ago and the SSL certificate was never issued for this domain.
Is there something I can do to push this certification to be implemented? I understand it should all be automated via Rebrandly.
We have just inspected your DNS configuration and found out there's an error with it:
comeu.org. 1798 IN A 220.127.116.11
comeu.org. 1798 IN A 18.104.22.168
comeu.org. 1798 IN A 22.214.171.124
When you configure a domain name to point Rebrandly, you are supposed to make sure you had deleted all the pre-existing A records. In this specific case, there is a misconfiguration in that you have an A record pointing to 126.96.36.199. This is not a Rebrandly IP, and this is likely the reason why Rebrandly wasn't able to generate an SSL certificate for your domain name.
Please fix this configuration problem (delete this DNS A record) and reach out to https://rebrandly.support/contact so that our Support team can manage to restart the verification procedure.
Thanks for reaching,
CTO at Rebrandly
It's been several days and my Rebrandly SSL Cert isn't working ("SSL Cert Not Active Yet"). Ideas? (elkhornsprings.org)
I am also facing the same problem with the last 2 enquirers. It has been several days since I’ve last added my subdomain (ask.jaybernie.com) and browsers are still detecting a problem with the SSL and labeled my link as an unsecured link.
Could my wildcard A record (*.jaybernie.com) be the cause of this?
Thanks in advance!