https://github.com/FiloSottile/mkcert Skip to content Toggle navigation Sign up * Product + Actions Automate any workflow + Packages Host and manage packages + Security Find and fix vulnerabilities + Codespaces Instant dev environments + Copilot Write better code with AI + Code review Manage code changes + Issues Plan and track work + Discussions Collaborate outside of code + Explore + All features + Documentation + GitHub Skills + Blog * Solutions + By Plan + Enterprise + Teams + Compare all + By Solution + CI/CD & Automation + DevOps + DevSecOps + Case Studies + Customer Stories + Resources * Open Source + GitHub Sponsors Fund open source developers + The ReadME Project GitHub community articles + Repositories + Topics + Trending + Collections * Pricing [ ] * # In this repository All GitHub | Jump to | * No suggested jump to results * # In this repository All GitHub | Jump to | * # In this user All GitHub | Jump to | * # In this repository All GitHub | Jump to | Sign in Sign up {{ message }} FiloSottile / mkcert Public * Notifications * Fork 1.9k * Star 37.7k A simple zero-config tool to make locally trusted development certificates with any names you'd like. mkcert.dev License BSD-3-Clause license 37.7k stars 1.9k forks Star Notifications * Code * Issues 78 * Pull requests 18 * Discussions * Actions * Projects 0 * Security * Insights More * Code * Issues * Pull requests * Discussions * Actions * Projects * Security * Insights FiloSottile/mkcert This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. master Switch branches/tags [ ] Branches Tags Could not load branches Nothing to show {{ refName }} default View all branches Could not load tags Nothing to show {{ refName }} default View all tags Name already in use A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch? Cancel Create 1 branch 14 tags Code * Clone HTTPS GitHub CLI [https://github.com/F] Use Git or checkout with SVN using the web URL. [gh repo clone FiloSo] Work fast with our official CLI. Learn more. * Open with GitHub Desktop * Download ZIP Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Launching Xcode If nothing happens, download Xcode and try again. Launching Visual Studio Code Your codespace will open once ready. There was a problem preparing your codespace, please try again. Latest commit @FiloSottile FiloSottile Drop "go vet" from CI due to false positives ... 1 2a46726 Apr 26, 2022 Drop "go vet" from CI due to false positives See golang/go#41205 2a46726 1 Git stats * 164 commits Files Permalink Failed to load latest commit information. Type Name Latest commit message Commit time .github AUTHORS LICENSE README.md cert.go go.mod go.sum main.go truststore_darwin.go truststore_java.go truststore_linux.go truststore_nss.go truststore_windows.go View code [ ] mkcert Installation macOS Linux Windows Supported root stores Advanced topics Advanced options Example S/MIME Mobile devices Using the root with Node.js Changing the location of the CA files Installing the CA on other systems README.md mkcert 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" Chrome and Firefox screenshot Using certificates from real certificate authorities (CAs) for development can be dangerous or impossible (for hosts like example.test, localhost or 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. Installation Warning: the rootCA-key.pem file that mkcert automatically generates gives complete power to intercept secure requests from your machine. Do not share it. macOS On macOS, use Homebrew brew install mkcert brew install nss # if you use Firefox or MacPorts. sudo port selfupdate sudo port install mkcert sudo port install nss # if you use Firefox Linux On Linux, first install certutil. 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 Windows 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. Supported root stores mkcert supports the following root stores: * macOS system store * Windows system store * Linux variants that provide either + update-ca-trust (Fedora, RHEL, CentOS) or + update-ca-certificates (Ubuntu, Debian, OpenSUSE, SLES) or + trust (Arch) * Firefox (macOS and Linux only) * Chrome and Chromium * Java (when JAVA_HOME is set) 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). Advanced topics Advanced options -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. Example mkcert -key-file key.pem -cert-file cert.pem example.com *.example.com S/MIME mkcert automatically generates an S/MIME certificate if one of the supplied names is an email address. mkcert filippo@example.com Mobile devices 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 mkcert -CAROOT. 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. Using the root with Node.js 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" Changing the location of the CA files 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 mkcert -CAROOT. 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 the CA on other systems 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. * Look for the rootCA.pem file in mkcert -CAROOT * copy it to a different machine * set $CAROOT to its directory * run mkcert -install 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 rootCA-key.pem. About A simple zero-config tool to make locally trusted development certificates with any names you'd like. mkcert.dev Topics windows macos linux tls firefox ios chrome https certificates localhost local-development root-ca Resources Readme License BSD-3-Clause license Stars 37.7k stars Watchers 450 watching Forks 1.9k forks Releases 14 Firefox Snap support for Ubuntu 22.04 Latest Apr 26, 2022 + 13 releases Packages 0 No packages published Used by 58 * @leexy76 * @AdeptMind * @rtgnx * @ryanmerolle * @DeterminateSystems * @samcday * @morgangallant * @ongood + 50 Contributors 39 * @FiloSottile * @adamdecaf * @herbygillot * @puiterwijk * @arp242 * @dennisameling * @frioux * @mikaelf * @jtdowney * @linux-china * @thedrow + 28 contributors Languages * Go 100.0% Footer (c) 2022 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.