Avatar of rascal
rascal
Flag for United States of America asked on

Browser doesn't like https://domainname.com but accepts https://www.domainname.com

We have installed a dedicated SSL certificate (our web host did on our shared web site) for our www.domainname.org. When folks visit https://www.domainname.org they view the site in secure mode no problem.

BUT - there are some google links to our site that link to https://domainname.org (without the www prefix). When users click on that link, they get a security warning from their browser stating that the site was set up for www.domainname.org.

Why is this happening? I understand that the common name assigned to an SSL means that is the specific address that it is for. But I am able to go to my own local web server where I installed a dedicated SSL and I can go to either https://www.mydomain.com or https://mydomain.com and I don't get a security warning.

Why do users clicking on the google link get the security error, but I don't when I go to my local site in SSl mode? Is it because they are clicking on a link, vs. my manually typing it in my browser? That is the only difference I can make out.

Any thoughts?
SSL / HTTPS

Avatar of undefined
Last Comment
Dave Baldwin

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Dave Baldwin

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
rascal

ASKER
Thanks DaveBaldwin,

The answer is contained in that post: some SSL issuers provide SSL certificates that work both WITH and WITHOUT the www. prefix, and at no extra charge. It's just part of the SSL certificate they generate.

For example, the SSL cert I got from Thawte works this way - it will work both with and/or without the www. prefix.

The problem SSL cert in this case was issued by SecureTrust and it requires the EXACT name - so if the SecureTrust certificate was issued as www.domainname.com, then that is the EXACT name that must be used.

Lesson learned - be sure you find out from the issuer whether the SSL certificate will work both WITH AND WITHOUT the www prefix - like Thawte does.
rascal

ASKER
Thanks Dave,
See my note above for more details.
Dave Baldwin

You're welcome and thanks for the points.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes