This popped up in Conversations today and I'm concerned
this post was submitted on 05 Jun 2026
12 points (100.0% liked)
Cybersecurity
10055 readers
116 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub
Notable mention to !cybersecuritymemes@lemmy.world
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It doesn't mean the website is using the same certificate. One can include as many domains as they want in a certificate, but nothing stops them from using something else.
But it's probable that they have some certificate renewal script that has reloaded the certificate on their website, but the service that you're connecting to still has the old certificate loaded.
Edit: yep, see https://bgp.he.net/certs#_SearchTab%3Fq=api.xmpp.jp , it looks like they did a renewal recently, but probably haven't reloaded their cert. So it'd probably be fine to accept it, or just wait a bit for them to realize and reload.