All 7 components done. Now the Astro pages:
Now update the landing page with all 19 tools:
Now diagnostics on all new files:
All clean. Here’s the full suite — 18 tools total, all 100% client-side:
| # | Tool | Route |
|---|---|---|
| 1 | SSL Certificate Decoder | /tools/certificate-decoder |
| 2 | Certificate Chain Validator | /tools/certificate-chain-validator |
| 3 | Certificate Expiry Checker | /tools/certificate-expiry-checker |
| 4 | Certificate Comparison | /tools/certificate-comparison |
| 5 | CSR Generator | /tools/csr-generator |
| 6 | CSR Decoder | /tools/csr-decoder |
| 7 | Key Pair Generator | /tools/key-pair-generator |
| 8 | SSH Public Key Parser | /tools/ssh-key-parser |
| 9 | PEM / DER Converter | /tools/pem-der-converter |
| 10 | PEM Formatter & Fixer | /tools/pem-formatter |
| 11 | Base64 Encoder / Decoder | /tools/base64 |
| 12 | ASN.1 Viewer | /tools/asn1-viewer |
| 13 | JWT Decoder | /tools/jwt-decoder |
| 14 | SSL Configuration Generator | /tools/ssl-config-generator |
| 15 | DANE / TLSA Record Generator | /tools/tlsa-record-generator |
| 16 | Cert → OpenSSL Commands | /tools/cert-to-openssl |
| 17 | CSR → OpenSSL Commands | /tools/csr-to-openssl |
| 18 | CT Log Lookup | /tools/ct-log-lookup |
Restart your dev server to pick up the new pages. That’s the full extent of what’s possible client-side for SSL/crypto tools.
upcoming things..
Two separate things here. Let me break them down:
Downloadable CLI tools you could offer for free:
These would be small open-source utilities users download and run locally. Great for lead gen — they use the tool, see QCecuring branding, and come back for the full product.
cert-scanner — CLI that scans a network range or list of domains, pulls their SSL certs, and outputs a report (expiry dates, issuers, key sizes, weak ciphers). Think nmap but focused on certificates. Python or Go single binary.
cert-monitor — Lightweight daemon/cron script that watches a list of domains and sends email/Slack alerts when certs are expiring within N days. Basically a self-hosted version of your Certificate Expiry Checker.
pem-toolkit — CLI Swiss army knife: decode certs, decode CSRs, validate chains, convert formats, generate key pairs. Everything your 18 browser tools do, but as a single CLI binary. pem-toolkit decode cert.pem, pem-toolkit chain *.pem, etc.
ssh-key-auditor — Scans ~/.ssh/, /etc/ssh/, or a directory tree for SSH keys, reports key types, sizes, ages, and flags weak keys (RSA < 2048, DSA). Ties into your SSH Key Management product.
openssl-cheatsheet — Not a tool per se, but a downloadable PDF/one-pager with the most common OpenSSL commands. High perceived value, easy to produce, great email gate.
Server-side tools that can’t work client-side (need a backend):
These require making network connections or accessing APIs that browsers block due to CORS/security:
| Tool | Why it needs a server |
|---|---|
| SSL Checker (enter domain → see cert details) | Browser can’t do a raw TLS handshake to an arbitrary domain. You need a server to connect to port 443, grab the cert chain, and return it. |
| OCSP Checker | Needs to fetch the OCSP responder URL from the cert and make an HTTP request to it. CORS blocks this from the browser. |
| CRL Checker | Same — needs to download the CRL file from the CA’s distribution point. CORS blocked. |
| CT Log Search (actual results, not just links) | crt.sh and Censys APIs have CORS restrictions. You’d need a proxy to fetch and return results. |
| Certificate Transparency Monitor | Needs to poll CT logs continuously and alert on new certs for a domain. Requires a persistent backend. |
| Domain SSL Grading (like SSL Labs) | Needs to test cipher suites, protocol versions, key exchange, etc. by actually connecting to the server. Requires a backend that does TLS handshakes with different configurations. |
| Email/SMTP TLS Checker | Check if a mail server supports STARTTLS. Needs a server to connect on port 25/587. |
| DNSSEC / DANE Validator | Needs to do actual DNS lookups for TLSA records and validate DNSSEC chains. Browser DNS APIs are too limited. |
My take:
For downloadable tools, the cert-scanner and pem-toolkit are the highest value. They’re genuinely useful, position QCecuring as a developer-friendly company, and create a natural upgrade path to your paid products.
For server-side tools, the SSL Checker (enter domain, see cert) is by far the highest traffic tool on every competitor site. If you ever add a small API endpoint (even a serverless function on Vercel), that’s the one to build first.
Want me to build any of the downloadable tools, or add a “coming soon” section for the server-side ones on the tools page?