Does this page generate or see my private key?
No. It only writes command text. The key is created on your machine when you run the command, and the page never receives a key, a certificate, or a password.
Writes the commands. Never touches your keys.
Pick a job, such as a key and CSR with Subject Alternative Names, a self-signed certificate, a PFX bundle, or a chain check, and get copy-ready OpenSSL 3 commands with every flag explained. Paste a command you found elsewhere to have it explained too.
Loading the toolbox.
You do not have to take our word that your data stays here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your data. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so a coding mistake could not quietly send your data elsewhere.
OpenSSL is the standard command-line toolkit for keys and certificates, and also one of the hardest tools to remember. The same job can be written several ways, older tutorials use commands that OpenSSL 3 has deprecated, and a single missing flag, such as the Subject Alternative Name, produces a certificate that every browser rejects. This page turns a task into the right commands and explains every flag in plain English.
It covers the jobs that come up again and again:
A private key is the most sensitive file a server owns: whoever holds it can impersonate the site. So this page never asks for one. It does not generate keys in the browser, it has no upload box for certificates, and it runs no cryptography at all. It only writes command text, which you run on the machine where the key should live. The key is created there and never travels.
That also means the commands work offline, in a locked-down network, or over SSH on the server itself. You can confirm in the Network tab that the page sends nothing while you use it.
Browsers decide whether a certificate matches a site by looking only at its Subject Alternative Names (SANs). The Common Name, the old place for the host name, is ignored. A certificate with a perfect Common Name and no SAN fails in every current browser with a name-mismatch error, which is the most common reason a hand-made certificate does not work.
OpenSSL 1.1.1 added the -addext option, so a SAN no longer needs a separate config file: -addext 'subjectAltName=DNS:example.com,DNS:www.example.com,IP:10.0.0.5'. The builder writes that for you. It copies the Common Name into the list, tells DNS names from IPv4 and IPv6 addresses, removes duplicates, and leaves out entries that a CA would reject, such as a wildcard that is not the whole leftmost label. It also reminds you that *.example.com does not cover example.com itself.
Keys are created with openssl genpkey, the modern command that handles every type. The older genrsa, rsa, and ec commands still run in OpenSSL 3 but are deprecated, and the decoder says so when you paste one.
A server fails to start, or a PFX import fails, when the key and the certificate do not belong together. The reliable test works for every key type: extract the public key from each file and hash it. openssl pkey -in example.com.key -pubout | openssl sha256 hashes the public half of the private key, and openssl x509 -in example.com.crt -noout -pubkey | openssl sha256 does the same for the certificate. If the two hashes are identical, the files match. The same check works on a CSR with openssl req -noout -pubkey.
Older guides compare the RSA modulus instead, which works only for RSA keys. The public-key hash covers RSA, EC, and Ed25519 alike.
-----BEGIN ...----- lines. Most Linux servers, nginx, and Apache use it. One file can hold several certificates.OpenSSL 3 protects a new PKCS#12 file with AES-256-CBC and PBKDF2 by default. Some older Windows and macOS importers only read the old RC2 and 3DES format, so the builder offers -legacy for those cases, and also for reading an old file that OpenSSL 3 refuses with an unsupported-algorithm error.
A server must send its own certificate plus every intermediate certificate between it and a trusted root. A missing intermediate is a classic problem: some browsers fetch it themselves and work, while other clients fail. openssl verify -CAfile root.pem -untrusted chain.pem example.com.crt checks the chain the way a strict client would. The root goes in -CAfile, and intermediates go in -untrusted, because putting an intermediate in the trusted file makes it a trust anchor and hides a missing-root problem. Adding -verify_hostname also checks the name.
To see what a live server actually sends, the remote-server task uses openssl s_client -connect example.com:443 -servername example.com -showcerts. The -servername flag matters: without it, a server that hosts many sites may return a different certificate.
The builder marks the risky steps. -out replaces an existing file without asking, so generating a key over the key of a live certificate breaks that certificate. A key written without a passphrase can be read by anyone with access to the file, so the commands add chmod 600. Passwords given as pass:... on the command line end up in shell history. On macOS, /usr/bin/openssl is LibreSSL, which lacks some OpenSSL 3 options, so install OpenSSL 3 if a flag is rejected. For hashing files, see Hash; for SSH keys, see SSH config.
Elsewhere in the toolbox: UUID, .gitignore, CSP, .htaccess, and more on the 2toolbox home page. Part of the 2suite.io privacy-first ecosystem.
No. It only writes command text. The key is created on your machine when you run the command, and the page never receives a key, a certificate, or a password.
OpenSSL 3, from the 3.0 long-term release onward. Most also run on OpenSSL 1.1.1. macOS ships LibreSSL as openssl, which lacks some options, so install OpenSSL 3 if a flag is rejected.
They do the same thing: write the private key without a passphrase. OpenSSL 3 renamed the option to -noenc and still accepts -nodes, which OpenSSL 1.1 and LibreSSL require.
Nobody trusts a self-signed certificate until you add it to the trust store of the browser or operating system. Check too that it has a Subject Alternative Name for the exact host you open.
Under CA/Browser Forum ballot SC-081, publicly trusted TLS certificates may be valid for at most 200 days from 2026-03-15, falling to 100 days from 2027-03-15 and 47 days from 2029-03-15. A self-signed certificate is not bound by that limit. Apple platforms reject any TLS server certificate valid for more than 825 days, even a self-signed one you trust.