|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Mkcert||40,210||7||5 days ago||15||April 26, 2022||109||bsd-3-clause||Go|
|A simple zero-config tool to make locally trusted development certificates with any names you'd like.|
|Certbot||29,782||178||116||2 days ago||92||June 08, 2022||529||other||Python|
|Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.|
|Nginx Admins Handbook||12,393||a year ago||1||mit||Shell|
|How to improve NGINX performance, security, and other important things.|
|HTTP, HTTP2, HTTPS, Websocket debugging proxy|
|Ponzu||4,887||3 years ago||4||January 02, 2020||24||bsd-3-clause||Go|
|Headless CMS with automatic JSON API. Featuring auto-HTTPS from Let's Encrypt, HTTP/2 Server Push, and flexible server framework written in Go.|
|A modern reverse proxy for node|
|Badssl.com||2,423||5 months ago||193||apache-2.0||HTML|
|:lock: Memorable site for testing clients against bad SSL configs.|
|Hyperfox||1,484||2 years ago||6||February 11, 2018||11||mit||Go|
|HTTP/HTTPS MITM proxy and recorder.|
|Sslsplit||1,448||a year ago||67||other||C|
|Transparent SSL/TLS interception|
mkcert is a simple tool for making locally-trusted development certificates. It requires no configuration.
$ mkcert -install Created a new local CA The local CA is now installed in the system trust store! The local CA is now installed in the Firefox trust store (requires browser restart)! $ mkcert example.com "*.example.com" example.test localhost 127.0.0.1 ::1 Created a new certificate valid for the following names - "example.com" - "*.example.com" - "example.test" - "localhost" - "127.0.0.1" - "::1" The certificate is at "./example.com+5.pem" and the key at "./example.com+5-key.pem"
Using certificates from real certificate authorities (CAs) for development can be dangerous or impossible (for hosts like
127.0.0.1), but self-signed certificates cause trust errors. Managing your own CA is the best solution, but usually involves arcane commands, specialized knowledge and manual steps.
mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates. mkcert does not automatically configure servers to use the certificates, though, that's up to you.
rootCA-key.pemfile that mkcert automatically generates gives complete power to intercept secure requests from your machine. Do not share it.
On macOS, use Homebrew
brew install mkcert brew install nss # if you use Firefox
sudo port selfupdate sudo port install mkcert sudo port install nss # if you use Firefox
On Linux, first install
sudo apt install libnss3-tools -or- sudo yum install nss-tools -or- sudo pacman -S nss -or- sudo zypper install mozilla-nss-tools
Then you can install using Homebrew on Linux
brew install mkcert
or build from source (requires Go 1.13+)
git clone https://github.com/FiloSottile/mkcert && cd mkcert go build -ldflags "-X main.Version=$(git describe --tags)"
or use the pre-built binaries.
curl -JLO "https://dl.filippo.io/mkcert/latest?for=linux/amd64" chmod +x mkcert-v*-linux-amd64 sudo cp mkcert-v*-linux-amd64 /usr/local/bin/mkcert
For Arch Linux users,
mkcert is available on the official Arch Linux repository.
sudo pacman -Syu mkcert
On Windows, use Chocolatey
choco install mkcert
or use Scoop
scoop bucket add extras scoop install mkcert
or build from source (requires Go 1.10+), or use the pre-built binaries.
If you're running into permission problems try running
mkcert as an Administrator.
mkcert supports the following root stores:
update-ca-trust(Fedora, RHEL, CentOS) or
update-ca-certificates(Ubuntu, Debian, OpenSUSE, SLES) or
To only install the local root CA into a subset of them, you can set the
TRUST_STORES environment variable to a comma-separated list. Options are: "system", "java" and "nss" (includes Firefox).
-cert-file FILE, -key-file FILE, -p12-file FILE Customize the output paths. -client Generate a certificate for client authentication. -ecdsa Generate a certificate with an ECDSA key. -pkcs12 Generate a ".p12" PKCS #12 file, also know as a ".pfx" file, containing certificate and key for legacy applications. -csr CSR Generate a certificate based on the supplied CSR. Conflicts with all other flags and arguments except -install and -cert-file.
Note: You must place these options before the domain names list.
mkcert -key-file key.pem -cert-file cert.pem example.com *.example.com
mkcert automatically generates an S/MIME certificate if one of the supplied names is an email address.
mkcert [email protected]
For the certificates to be trusted on mobile devices, you will have to install the root CA. It's the
rootCA.pem file in the folder printed by
On iOS, you can either use AirDrop, email the CA to yourself, or serve it from an HTTP server. After opening it, you need to install the profile in Settings > Profile Downloaded and then enable full trust in it.
For Android, you will have to install the CA and then enable user roots in the development build of your app. See this StackOverflow answer.
Node does not use the system root store, so it won't accept mkcert certificates automatically. Instead, you will have to set the
NODE_EXTRA_CA_CERTS environment variable.
export NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem"
The CA certificate and its key are stored in an application data folder in the user home. You usually don't have to worry about it, as installation is automated, but the location is printed by
If you want to manage separate CAs, you can use the environment variable
$CAROOT to set the folder where mkcert will place and look for the local CA files.
Installing in the trust store does not require the CA key, so you can export the CA certificate and use mkcert to install it in other machines.
$CAROOTto its directory
Remember that mkcert is meant for development purposes, not production, so it should not be used on end users' machines, and that you should not export or share