# google says the sdmb is an unsafe site

**URL:** <https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512>\
**Category:** About This Message Board\
**Created:** [February 14, 2019, 1:05am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512 "2019-02-14T01:05:05Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Doug\_K](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@Doug\_K](https://boards.straightdope.com/u/Doug_K)\
**Post date:** [February 15, 2019, 3:43pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/21 "2019-02-15T15:43:42Z")

</div>

The fact that not everyone gets those warnings makes me wonder if it could be a weird caching issue. Browser aren’t supposed to cache certificates, but there’s a couple of comments in [this thread on Super User](https://superuser.com/questions/390664/do-web-browsers-cache-ssl-certificates) that indicates maybe sometimes they do anyway.

---

<div class="post-metadata">

**Author:** ![TubaDiva](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tubadiva/32/507_2.png) [@TubaDiva](https://boards.straightdope.com/u/TubaDiva)\
**Post date:** [February 15, 2019, 5:14pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/22 "2019-02-15T17:14:57Z")

</div>

I’ve alerted management to this situation again. They were looking at it yesterday. Guess they’re not finished.

Jenny  
your humble TubaDiva  
Administrator

---

<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:** [February 15, 2019, 6:48pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/23 "2019-02-15T18:48:43Z")

</div>

Latest Chrome, updated Windows 10 Pro, no issues. But I am using a number of security add-ins, Trustwave, Privacy Badger, and Disconnect, which block a lot of malicious stuff.

---

<div class="post-metadata">

**Author:** ![Slow\_Moving\_Vehicle](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/slow_moving_vehicle/32/291_2.png) [@Slow\_Moving\_Vehicle](https://boards.straightdope.com/u/Slow_Moving_Vehicle)\
**Post date:** [February 15, 2019, 7:02pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/24 "2019-02-15T19:02:26Z")

</div>

Awright, which one of you goombahs told Google about the squid and the goat?

---

<div class="post-metadata">

**Author:** ![TubaDiva](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tubadiva/32/507_2.png) [@TubaDiva](https://boards.straightdope.com/u/TubaDiva)\
**Post date:** [February 16, 2019, 3:37am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/25 "2019-02-16T03:37:03Z")

</div>

Things do appear to have resolved. I think they renewed the security certificate, but don’t quote me on that.

Sorry for the inconvenience.

Jenny  
your humble TubaDiva  
Administrator

---

<div class="post-metadata">

**Author:** ![bobot](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bobot/32/21622_2.png) [@bobot](https://boards.straightdope.com/u/bobot)\
**Post date:** [February 16, 2019, 12:48pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/26 "2019-02-16T12:48:40Z")

</div>

SDMB opened today with no errors. Thanks!

---

<div class="post-metadata">

**Author:** ![Johnny\_L.A](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/johnny_l.a/32/1084_2.png) [@Johnny\_L.A](https://boards.straightdope.com/u/Johnny_L.A)\
**Post date:** [February 16, 2019, 2:54pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/27 "2019-02-16T14:54:24Z")

</div>

> [@TubaDiva](#):
>
> Things do appear to have resolved. I think they renewed the security certificate…

😛

---

<div class="post-metadata">

**Author:** ![kopek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/kopek/32/337_2.png) [@kopek](https://boards.straightdope.com/u/kopek)\
**Post date:** [February 16, 2019, 11:09pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/28 "2019-02-16T23:09:30Z")

</div>

> [@bobot](#):
>
> SDMB opened today with no errors. Thanks!

Well, one could consider (insert the name of your favorite thread here) to be an error. But technically it looks to be working better. 😉

---

<div class="post-metadata">

**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\
**Post date:** [February 17, 2019, 10:46am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/29 "2019-02-17T10:46:53Z")

</div>

> [@TubaDiva](#):
>
> Things do appear to have resolved. I think they renewed the security certificate, but don’t quote me on that.

(In chrome) I’m still seeing the “not secure” prefix to the URL, and when I begin creating a post, like this one, it changes to red. Personally, I’m not worried, but others might not be so cavalier about it.

---

<div class="post-metadata">

**Author:** ![chappachula](https://avatars.discourse-cdn.com/v4/letter/c/d2c977/32.png) [@chappachula](https://boards.straightdope.com/u/chappachula)\
**Post date:** [February 17, 2019, 11:15am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/30 "2019-02-17T11:15:56Z")

</div>

> [@TubaDiva](#):
>
> Sorry for the inconvenience.
> 
> Jenny  
> your humble TubaDiva  
> Administrator

No, Jenny. _We_ are sorry that we inconvenienced _you._

Seriously…a big THANK YOU from all of us…for the work you put in every day to keep this place up and running.

(signed,  
a couple of thousand Dopers.)

---

<div class="post-metadata">

**Author:** ![Hilarity\_N.Suze](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/hilarity_n.suze/32/6223_2.png) [@Hilarity\_N.Suze](https://boards.straightdope.com/u/Hilarity_N.Suze)\
**Post date:** [February 18, 2019, 1:00am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/31 "2019-02-18T01:00:25Z")

</div>

I’m still getting them. Do I have to like clear my cache or something?

---

<div class="post-metadata">

**Author:** ![Kent\_Clark](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/kent_clark/32/105_2.png) [@Kent\_Clark](https://boards.straightdope.com/u/Kent_Clark)\
**Post date:** [February 18, 2019, 2:32am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/32 "2019-02-18T02:32:13Z")

</div>

Well, shucks. Now I’m getting Sultantheme’s skin AND a Not Secure warning.

---

<div class="post-metadata">

**Author:** ![sps49sd](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@sps49sd](https://boards.straightdope.com/u/sps49sd)\
**Post date:** [February 18, 2019, 4:21am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/33 "2019-02-18T04:21:53Z")

</div>

I get the unsecured message on Firefox if I attempt login on a page not prefixed with ‘https’.

---

<div class="post-metadata">

**Author:** ![DrDeth](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@DrDeth](https://boards.straightdope.com/u/DrDeth)\
**Post date:** [February 18, 2019, 5:25am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/34 "2019-02-18T05:25:51Z")

</div>

> [@chappachula](#):
>
> No, Jenny. _We_ are sorry that we inconvenienced _you._
> 
> Seriously…a big THANK YOU from all of us…for the work you put in every day to keep this place up and running.
> 
> (signed,  
> a couple of thousand Dopers.)

Actually the Security certificate is a really critical thing, so we did\* her \*a favor.

But we do appreciate her labors, too.

---

<div class="post-metadata">

**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\
**Post date:** [February 18, 2019, 5:46am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/35 "2019-02-18T05:46:03Z")

</div>

Maybe I spoke too soon (post #29). The problem now seems to be fixed and I don’t see any “not secure” messages in any color.

---

<div class="post-metadata">

**Author:** ![TubaDiva](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tubadiva/32/507_2.png) [@TubaDiva](https://boards.straightdope.com/u/TubaDiva)\
**Post date:** [February 18, 2019, 3:39pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/36 "2019-02-18T15:39:27Z")

</div>

> [@kunilou](#):
>
> Well, shucks. Now I’m getting Sultantheme’s skin AND a Not Secure warning.

Has any of this resolved for you?

If any of you are still having difficulties with the site, please let me know. Say something here or send me an email [tubadiva@aol.com](mailto:tubadiva@aol.com)

Jenny  
your humble TubaDiva  
Administrator

---

<div class="post-metadata">

**Author:** ![sps49sd](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@sps49sd](https://boards.straightdope.com/u/sps49sd)\
**Post date:** [February 20, 2019, 4:01am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/37 "2019-02-20T04:01:30Z")

</div>

I still get the red slash through the lock on a page that doesn’t load as ‘https://’, and Firefox will prevent my login if I try. But if I get to a page that is secure and has a login button, I can and then all pages are secure.

---

<div class="post-metadata">

**Author:** ![engineer\_comp\_geek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/engineer_comp_geek/32/504_2.png) [@engineer\_comp\_geek](https://boards.straightdope.com/u/engineer_comp_geek)\
**Post date:** [February 20, 2019, 5:25am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/38 "2019-02-20T05:25:38Z")

</div>

How exactly are you getting to a page that loads as http instead of https?

---

<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:** [February 20, 2019, 7:46am UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/39 "2019-02-20T07:46:49Z")

</div>

> [@engineer\_comp\_geek](#):
>
> How exactly are you getting to a page that loads as http instead of https?

For me it just seemed to randomly happen–but this was earlier when they were still trying to fix things, so I assumed it was a temporary thing.

---

<div class="post-metadata">

**Author:** ![engineer\_comp\_geek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/engineer_comp_geek/32/504_2.png) [@engineer\_comp\_geek](https://boards.straightdope.com/u/engineer_comp_geek)\
**Post date:** [February 20, 2019, 4:34pm UTC](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512/40 "2019-02-20T16:34:57Z")

</div>

As far as I am aware, all of the http vs https issues have been fixed (I don’t personally get to talk to the tech guys though). We shouldn’t be serving up any pages as http at this point. They should all be https.

[Previous page](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512.md?page=1)

[Next page](https://boards.straightdope.com/t/google-says-the-sdmb-is-an-unsafe-site/829512.md?page=3)
