SSL Certificate Creator

Create self-signed SSL certificates for free

Features

Instantly generate self-signed certificates

Output the certificate, private key, and CSR all at once without a certificate authority

Choose key length and signature method

Supports 2048/4096 bits and four methods such as SHA-256

Set validity from 1 to 10 years

Flexibly set the certificate's expiry to match your testing needs

Download three formats on the spot

Copy and save the private key, certificate, and CSR in separate tabs

How to use

Enter the certificate's issuance details

Enter the target's details such as the common name (domain name), organization name, and country code

Specify key length and signature method

Choose the key size, signature algorithm, and validity period from the dropdowns

Create the certificate with the generate button

Press the generate button to create the certificate, private key, and CSR in the browser

Get the content from each tab

Copy or download from the private key, certificate, and CSR tabs

Use cases

Verify local HTTPS

Quickly prepare a certificate to check HTTPS communication in a development environment

Prepare to build a test environment

Assign a provisional certificate to a staging or internal verification server

Prototype a CSR template in advance

Check the field layout and entered values of a CSR before applying for a formal certificate

As SSL learning material

Use in training and hands-on sessions to learn the structure of certificates, private keys, and CSRs

Basics

What is a Self-Signed Certificate?

A self-signed certificate is an SSL certificate signed by yourself without receiving a signature from a Certificate Authority (CA). While it enables encrypted communication, it is often called a self-signed certificate because it has not undergone third-party identity verification.

Why It Cannot Be Used on Production Sites

Browsers verify certificates by tracing signatures from trusted Certificate Authorities. Self-signed certificates trigger a "This connection is not secure" warning. They should be limited to development, testing environments, or internal systems.