-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sha384.badssl.com and sha512.badssl.com both have expired certificates #501
Comments
Also expired includes:
(though the last two were already reported in #467) |
Fix failing tests due to chromium/badssl.com#501
Any update ? |
I was intending to make an issue for this, but it seems someone already has. I can confirm that the certificate with fingerprint D9:D0:1E:C5:5C:10:D0:A6:9C:96:17:C9:F1:31:DB:04:9F:D9:95:59 appears to have expired on 4/1/2022. |
As of today, the https://rsa8192.badssl.com/ has also expired. Any chance that this will get renewed? |
sha384.badssl.com and sha512.badssl.com both have expired certificates as of April 1st, 2022.
The text was updated successfully, but these errors were encountered: