# Straight Dope: Site Not Secure, Invalid Certificate, Expired Certificate

**URL:** <https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722>\
**Category:** About This Message Board\
**Created:** [December 7, 2018, 12:17am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722 "2018-12-07T00:17:37Z")\
**Posts on this page:** 9\
**Page:** 3

<div class="post-metadata">

**Author:** ![Tierce](https://avatars.discourse-cdn.com/v4/letter/t/ea5d25/32.png) [@Tierce](https://boards.straightdope.com/u/Tierce)\
**Post date:** [December 13, 2018, 12:33am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/41 "2018-12-13T00:33:45Z")

</div>

I’ve been getting a similar error from [arrow.scrolltotop.com](http://arrow.scrolltotop.com) for a while now. Presumably something to do with the arrow on the new theme.

---

<div class="post-metadata">

**Author:** ![kayT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/kayt/32/3633_2.png) [@kayT](https://boards.straightdope.com/u/kayT)\
**Post date:** [December 13, 2018, 12:38am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/42 "2018-12-13T00:38:21Z")

</div>

This has happened before. More than once and quite a while ago, IIRC. It doesn’t seem to be a big deal. Firefox never stopped me from getting on the site, just nagged at me.

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [December 13, 2018, 2:42am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/43 "2018-12-13T02:42:07Z")

</div>

> [@Tierce](#):
>
> I’ve been getting a similar error from [arrow.scrolltotop.com](http://arrow.scrolltotop.com) for a while now. Presumably something to do with the arrow on the new theme.

That’s a slightly different issue. The people who make the arrow updated their site (including adding HTTPS), and it made the arrow here stop working.

Personally, I always thought it was overkill. A nice “scroll to top” button is really easy to make locally, not requiring you to run a script from another site. Sure, it wouldn’t have that fancy “watch it scroll up” effect, but it would work.

---

<div class="post-metadata">

**Author:** ![Max\_S](https://avatars.discourse-cdn.com/v4/letter/m/46a35a/32.png) [@Max\_S](https://boards.straightdope.com/u/Max_S)\
**Post date:** [January 11, 2020, 12:07am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/44 "2020-01-11T00:07:41Z")

</div>

I noticed that your site certificate expired again. Today’s the day: 1/9/19-1/10/20.

~Max

---

<div class="post-metadata">

**Author:** ![KarlGauss](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/karlgauss/32/3713_2.png) [@KarlGauss](https://boards.straightdope.com/u/KarlGauss)\
**Post date:** [January 11, 2020, 12:15am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/45 "2020-01-11T00:15:34Z")

</div>

Likewise. Just got a warning when I tried to connect five minutes ago (but interestingly only when I accessed the boards on my Mac but not on a Windows machine).

---

<div class="post-metadata">

**Author:** ![Morgyn](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/morgyn/32/3041_2.png) [@Morgyn](https://boards.straightdope.com/u/Morgyn)\
**Post date:** [January 11, 2020, 12:17am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/46 "2020-01-11T00:17:38Z")

</div>

I’m on Windows, using Chrome, and I just got it, too.

---

<div class="post-metadata">

**Author:** ![Darren\_Garrison](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/darren_garrison/32/92_2.png) [@Darren\_Garrison](https://boards.straightdope.com/u/Darren_Garrison)\
**Post date:** [January 11, 2020, 12:20am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/47 "2020-01-11T00:20:08Z")

</div>

_Sooooo_ much competence…

---

<div class="post-metadata">

**Author:** ![Max\_S](https://avatars.discourse-cdn.com/v4/letter/m/46a35a/32.png) [@Max\_S](https://boards.straightdope.com/u/Max_S)\
**Post date:** [January 11, 2020, 12:31am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/48 "2020-01-11T00:31:49Z")

</div>

Note that an expired SSL certificate does not mean your connection is unencrypted. Certificates expire to force websites to keep up to date with the latest SSL standards, sort of like how doctors have to renew their licenses every year. A doctor without a one-day expired license probably still knows how to treat patients (I’m ignoring the legal repercussions), and a SSL-certificate one day expired is still quite secure.

Correct me if I’m wrong.

~Max

---

<div class="post-metadata">

**Author:** ![Colibri](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/colibri/32/1841_2.png) [@Colibri](https://boards.straightdope.com/u/Colibri)\
**Post date:** [January 11, 2020, 1:52am UTC](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722/49 "2020-01-11T01:52:44Z")

</div>

Since there is a current thread on this, I’ve closed this old one.

[Previous page](https://boards.straightdope.com/t/straight-dope-site-not-secure-invalid-certificate-expired-certificate/825722.md?page=2)
