| Common Name | forum.amiga.org |
| Not Before | 09/03/2020, 13:46:55 (British Summer Time) |
| Not After | 07/06/2020, 14:46:55 (British Summer Time) |
| SHA-256 fingerprint | 6D:C2:32:AB:19:8A:68:43:F0:D9:BA:E7:4A:F0:CE:F4:BE:65:D5:A1:CF:AA:91:E1:AD:70:CA:7F:E6:A1:C8:43 |
| SHA-1 fingerprint | 39:14:C4:8F:03:1D:F0:76:79:02:6F:ED:98:F3:43:1B:00:1B:8B:0A |
Root site certificate is still borked here.
https://www.amiga.org/
So it must be a website you don't really care much about, since you still haven't fixed the certificate, 3 days after expiration... which we kinda knew already, as it obviously only exists for one purpose, to distract potential customers from a competing vendor.
You have way to much time on your hands.
I personally have all mine automated to avoid any of this. Does that then mean, I don't care about my sites.
Well, I _am_ talking about AmigaKit's websites, not mine. I see now that you have finally updated certificate for amigastore.com, after it was expired for what... 4 days? And then you come here to uhm, brag about your splendid automation? Awesome. Guess what else is automated? My monitoring of AmigaKit's services and their certificates.
I have nothing to do with Amigakits domains.
However you apparently do, as you seem to have an opinion on everything and follow them closely.
I never accused you of having anything to do with AmigaKit domains (they're all out-sourced), my gripes here are AmigaKit websites, services and certificates... like this very site here, where you are "AmigaKit support" and "Administrator", and rumours on town is that you're the only technical person around at AmigaKit. Perhaps you should implement your automation for the AmigaKit sites then? Btw, it's a little fascinating that there are so many individual certificates, one for each and every service.
Yup, however it doesn't take any of my time... I'm monitoring services anyways, adding amigakit sites didn't cost anything.