The maintainers of the big web browsers have pretty strict rules for CAs in this list. If any one of them gets caught issuing only one certificate maliciously, they are out of business.

And all CAs are required to publish each certificate in multiple public, cryptographically signed ledgers.

Sure, there is a history of CAs issuing certificates to people that shouldn’t have them (e.g. for espionage), but that is almost impossible now.

For 3 more months or so, you can’t buy them in april 2026 anymore

Short lifespans are also great when domains change their owner. With a 3 year lifespan, the old owner could possibly still read traffic for a few more years.

When the lifespan ist just 30-90 days, that risk is significatly reduced.

No, these are completely separate issues.

• CRL: protect against certificates that have their private key compromised
• CT: protect against incompetent or malicious Certificate Authorities.

This is just one example why we have certificate transparency. Revocation wouldn’t be useful if it isn’t even known which certificates need revocation.

The National Informatics Centre (NIC) of India, a subordinate CA of the Indian Controller of Certifying Authorities (India CCA), issues rogue certificates for Google and Yahoo domains. NIC claims that their issuance process was compromised and that only four certificates were misissued. However, Google is aware of misissued certificates not reported by NIC, so it can only be assumed that the scope of the breach is unknown.

Source

There are some nameserver providers that have an API.

When you register a domain, you can choose which nameserver you like. There are nameservers that work with certbot, choose one that does.

The only disadvantage I see is that all my personal subdomains (e.g. immich.name.com and jellyfin) are forever stored in a public location. I wouldn’t call it a privacy nightmare, yet it isn’t optimal.

There are two workarounds:

• do not use public certificates
• use wildcard certificates only

The best approach for securing our CA system is the “certificate transparency log”. All issued certificates must be stored in separate, public location. Browsers do not accept certificates that are not there.

This makes it impossible for malicious actors to silently create certificates. They would leave traces.

The “accepted anwer” feature seems very nice, i would love to see this implemented in other fediverse projects too.

The factor is about 3 (75 to 212 motorcycle related deaths), that seems a plausible deviation between different countries.

I’d recommend to try a few helmets. I once bought the cheapest helmet the store had to offer … only to return it next day.

Please … don’t buy a helmet on Amazon. Try it out, find one that fits, take it for a test drive.

Hours of travel time would likely be a good fit too.

It would be interesting to see different motorcycle stats. Those 100+ horsepower beasts are probably in another ballpark than regular commuter bikes (e.g. 125cc).

Just guessing, the lower speed might help.

Edit: found a statistic that says otherwise. Translated from german. Original source

• Car: 1.57
  → 2.53 per billion miles

• Bus: 0.13
  → 0.21 per billion miles

• Train: 0.03
  → 0.048 per billion miles

• Airplane: 0.01
  → 0.016 per billion miles

• Bicycle: 9.8
  → 15.77 per billion miles

• Ship: 0.1
  → 0.16 per billion miles

• Tram: 0.19
  → 0.31 per billion miles

• Motorcycle: 46.5
  → 74.83 per billion miles

Edit 2: Interesting how my german statistic shows way lower numbers than the original statistic.