when I check into BC I get this message;

NET::ERR_CERT_DATE_INVALID
Subject: http://www.bookcrossing.com

Issuer: RapidSSL RSA CA 2018

Expires on: 6 okt. 2020

Current date: 6 okt. 2020

Who do I contact to look into this?

when I check into BC I get this message;

NET::ERR_CERT_DATE_INVALID
Subject: http://www.bookcrossing.com

Issuer: RapidSSL RSA CA 2018

Expires on: 6 okt. 2020

Current date: 6 okt. 2020

Will someone look into this?

Yes, I just got the same message!

The error I get is:

Your connection isn't private
Attackers might be trying to steal your information from http://www.bookcrossing.com (for example, passwords, messages, or credit cards).
NET::ERR_CERT_DATE_INVALID

I clicked under that, finally, to look further and saw the option to connect unsafely. How weird. Also, as I type this right now, up in my browser box, in red print it says *Not secure* and the http part of the address is crossed off in red, as well.

I have no idea what this means or what I am supposed to do. The link to BC is the same one I have used since I first joined. So what has changed?

I get the same message, and it indicates that BC's security certificate has expired and not been renewed.

Oh, that's interesting. I also just posted a note through the *contact us* link to the admin so maybe things will change soon. On my error message, I just noticed that there is a button, below it, labelled *Advanced* and that is how I was able to connect but every time I post something, I get the error message page again and have to go through that button to get back here.

it indicates that BC's security certificate has expired and not been renewed.

That's correct. Ardik has been notified, and he's on it.

That's correct. Ardik has been notified, and he's on it.

Thank you Moem.

as this is the first time today that I logged on and did not get that error message.

Thanks, Ardik and whatever other techno gods did the fixing! :-)

but when I see those sorts of messages, even though I know it's probably just a certificate expiration, I do not risk continuing on to the website.

I just sent an email directly to Support.