SSL Certificate installed for 1 of 2 domains

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: www.campallennh.org

I ran this command: https://campallennh.org

It produced this output: unsecure privacy error message (Though, when using https://www.campallennh.org, it connects to the website just fine.)

My web server is (include version): ?

The operating system my web server runs on is (include version): Mac?

My hosting provider, if applicable, is: Network Solutions

I can login to a root shell on my machine (yes or no, or I don't know): I don't know

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): ?

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): ?

2

Hello @campallennh, welcome to the Let's Encrypt community. :slightly_smiling_face:

As you can see here https://decoder.link/sslchecker/www.campallennh.org/443
and here Hardenize Report: campallennh.org

The certificate for www.campallennh.org only contains itself for the SANs,
you need to also add campallennh.org to the SANs thus having both names.

Edit:

And it seems your server is Squarespace.

$ curl -Ii http://www.campallennh.org/.well-known/acme-challenge/sometestfile
HTTP/1.1 403 Forbidden
Connection: close
Server: Squarespace
X-Contextid: iF7mL5Yi/LIJBGej3
X-Sqsp-Edge: true
Date: Tue, 12 May 2026 16:14:22 GMT
Content-Length: 1434
Content-Type: text/html; charset=utf-8
3

Is this something we do on the Squarespace end?

4

Likely yes, I do not know how Squarespace functions.

5

Can you please explain this further? How can this be updated? I don't see SANs on Squarespace settings...

6

Sorry I cannot, so kindly wait for more knowledgeable Let's Encrypt community volunteers to assist.

7

You may have better luck trying to deal with Squarespace support. (In theory that's who you're paying to get this working, isn't it?) People here aren't likely to have a lot of experience with them, though maybe someone does. We can try to describe what's happening, though:

From an internet standards perspective, the names www.campallennh.org and campallennh.org are completely separate, and might not have anything to do with each other. Now, most users probably expect that they'll end up both leading to the same place, sure, but that's just because most website operators set them up that way.

So, if you want both those names to work, you need to have your hosting company configure a certificate and what you want to have happen for both of those names. I would expect that most would make it fairly straightforward, since it's a common thing to want. But it may be that you need to specifically configure it somewhere.

8

Thanks, @petercooperjr, for your reply. We'll reach out to Squarespace for further support. (We're under new leadership and working on cleaning up platforms, etc.)