Skip to content
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

Open
SalusaSecondus opened this issue Apr 8, 2022 · 6 comments
Assignees

Comments

@SalusaSecondus
Copy link

sha384.badssl.com and sha512.badssl.com both have expired certificates as of April 1st, 2022.

sha384_expired

sha512_expired

pufferffish added a commit to idris-community/idris2-tls that referenced this issue Apr 14, 2022
@gurnec
Copy link

gurnec commented May 11, 2022

Also expired includes:

  • 1000-sans
  • 10000-sans
  • no-subject
  • no-common-name

(though the last two were already reported in #467)

@christhompson christhompson self-assigned this May 17, 2022
szh added a commit to cyberark/conjur-api-python that referenced this issue May 20, 2022
szh added a commit to cyberark/conjur-api-python that referenced this issue May 23, 2022
@tranb3r
Copy link

tranb3r commented Jul 25, 2022

Any update ?

@emabrey
Copy link

emabrey commented Jul 26, 2022

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.

@stefanpantic-pdftools
Copy link

As of today, the https://rsa8192.badssl.com/ has also expired. Any chance that this will get renewed?

@djp3
Copy link

djp3 commented Jul 30, 2024

@djp3
Copy link

djp3 commented Jul 30, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants