中文

About ssl.sh

Last verified

ssl.sh is an independent SSL/TLS resource for anyone who runs HTTPS: developers, sysadmins and the people who get paged when a certificate expires.

What we do

  • Tools. Check any certificate with curl ssl.sh/example.com or in the browser. Generate CSRs, decode certificates, convert formats and build TLS configs. Tools that touch private keys run entirely in your browser.
  • Knowledge. Every page starts with a direct answer, lists the date it was last verified, and links to primary sources: RFCs, the CA/Browser Forum Baseline Requirements, root program policies and CA announcements.
  • Monitoring (in development). Certificate lifetimes are shrinking to 47 days by 2029. ssl.sh Monitor will check your certificates on a schedule and alert you before something breaks. It is not open for sign-up yet.

Editorial policy

Who writes ssl.sh

ssl.sh is written and maintained by ClientHello, the pen name of a senior technology industry practitioner. The author page explains how articles are researched and why the site uses a pen name.

How pages are verified

Articles are drafted with AI assistance. Before a page is published, every factual claim (dates, limits, defaults, command options) is checked against a primary source: the relevant RFC, the CA/Browser Forum Baseline Requirements and ballots, the root program policies of Chrome, Mozilla, Apple and Microsoft, and the documentation of the software or vendor involved. Each page lists those sources and shows the date it was last verified. Certificate prices are copied by hand from each seller's own website, together with the date and the page where we checked them.

How often content is updated

Root store and CA data are refreshed weekly from the root programs, and the State of TLS report is rebuilt every month from a fresh scan. Articles are re-checked whenever a relevant RFC, ballot or root program policy changes. The "last verified" date only moves when a page has actually been checked against its sources again, not when we fix a typo.

Corrections

If something is wrong or out of date, email hello@ssl.sh with the page address and, if you can, the source that disagrees. Confirmed errors are fixed and the page's verified date is updated. Security issues go through /.well-known/security.txt.

How ssl.sh makes money

ssl.sh earns money in two ways. First, some buying guides and certificate comparison pages contain affiliate links: if you buy through one, the seller may pay us a commission at no extra cost to you. Affiliate links never affect sort order or rankings: tables are sorted by the lowest verified price, and sellers that pay nothing are listed too. Details are in the affiliate disclosure. Second, ssl.sh Monitor has paid subscription plans for larger numbers of domains; small setups can use the free plan (see pricing).

Independence

ssl.sh is not a certificate authority and is not affiliated with any CA, with acme.sh or with testssl.sh. Commercial relationships never change test results or rankings.

Contact

Email hello@ssl.sh. Security reports: see /.well-known/security.txt.