Using a custom domain name with a secure SSL connection

Last modified: 2018-05-16 16:33:50 +0200

If you like, you can set up your own URL instead of Be aware that our aNewSpring app only works with the secure connection, so it will not be possible to log in with an own domain name that doesn't use HTTPS. See the solution at step 4. 

1) Create a sub domain in your domain settings

This should always be a sub domain of an existing domain. If your own website is, then you could for example user instead of

2) Change the DNS settings of your domain.

The sub domain that you would like to use ( should become a CNAME of If you don't know how to set this up, the hosting company of your domain could help you with that.
If you use multiple subenvironments, it is very important to always use the standard aNewSpring URL as a CNAME, so this way:

aNewSpring URL
own URL
Standard environment
Subenvironment 1
Subenvironment 2

3) Notify us about your sub domain 

Send us an email at and let us know which URL you would like to use and for which subenvironment we should set this up. Due to our setup you will be directed to the right subenvironment, also if you have set multiple subenvironments as the same CNAME.

4) Set up an SSL certificate (HTTPS)

Your new custom domain won't simply work with a secure SSL connection. With SSL sensitive information will be encrypted, so this can't be intercepted. You can recognise websites that use an SSL certificate by HTTPS in the link. Our aNewSpring app only works with the secure connection, so it will not be possible to log in with an own domain name that doesn't use HTTPS. You can provide us with an SSL certificate that we will have installed by our hosting provider. To cover the costs, we charge 250 USD per installation.

A) Generate a CSR

You will need a CSR (Certificate Signing Request) to request the certificate and the hosting provider of your domain will be able to help you with this. You can use for example this CSR generator.

B) Purchase an SSL certificate and send it to us

If you use multiple subenvironments like in the example at step 2, it's best to purchase a Wildcard certificate. With this kind of certificate all subdomains of e.g. * are covered. We would like to receive the SSL certificate with its private key (without a passphrase) in .crt, .ca-bundle or .pem format. Next we can get it installed on our servers.

We arrange the certificate through SNI and some old browsers don't support this. You will find more information about which browsers are supported on this website.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.
Can you please tell us how we can improve this article?