TLS Config Generator

Secure TLS settings for nginx, Apache, HAProxy or IIS, following Mozilla's guidelines: protocols, ciphers, post-quantum key exchange, HSTS.

Copy-paste TLS settings for nginx, Apache, HAProxy or IIS that follow Mozilla's Server Side TLS guidelines (version 6.0): the protocols, ciphers and key exchange groups to allow, HSTS, and redirecting plain HTTP. Pick "intermediate" unless you know every client supports TLS 1.3. Afterwards, check the result with the TLS Certificate Checker and Security Headers.

Host name

HSTS (two years)

Redirect HTTP to HTTPS

Post-quantum key exchange (needs OpenSSL 3.5+)

OCSP stapling

Configuration

980 characters · 980 bytes UTF-8

# Mozilla intermediate profile (Server Side TLS 6.0), nginx 1.25.1 or later
http {
    server {
        listen 80;
        listen [::]:80;
        server_name example.com;
        return 301 https://$host$request_uri;
    }

    server {
        listen 443 ssl;
        listen [::]:443 ssl;
        http2 on;
        server_name example.com;

        ssl_certificate     /etc/ssl/example.com/fullchain.pem;
        ssl_certificate_key /etc/ssl/example.com/privkey.pem;

        ssl_protocols TLSv1.2 TLSv1.3;
        ssl_ecdh_curve X25519:prime256v1:secp384r1;
        ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305;
        ssl_prefer_server_ciphers off;

        ssl_session_timeout 1d;
        ssl_session_cache shared:TLS:10m;

        add_header Strict-Transport-Security "max-age=63072000" always;
    }
}

nginx before 1.25.1: drop "http2 on;" and write "listen 443 ssl http2;" instead.

The TLS 1.3 cipher suites are left at OpenSSL's defaults, which are the three Mozilla recommends; nginx's ssl_ciphers only affects TLS 1.2.

Test with nginx -t before reloading (nginx -s reload or systemctl reload nginx).

HSTS makes browsers refuse plain HTTP to this host for two years. Turn it on only when HTTPS works everywhere on it; start with a short max-age (300) if you're unsure, and add includeSubDomains only when every subdomain has HTTPS too.