TLS Configuration Generator — générateur de configurations TLS
Choisissez votre serveur et sa version, sélectionnez un profil, puis copiez une configuration construite d’après les recommandations TLSRef Server Side TLS, qui prennent la suite de celles de Mozilla. L’hybride post-quantique X25519MLKEM768 est activé partout où votre version du serveur peut le nommer. Vous avez déjà une configuration en service ? Collez-la dans « Expliquer ma configuration ».
100 % local : tout s’exécute dans votre navigateur, rien n’est envoyé à aucun serveur
Laissez vide pour utiliser la version actuelle, 1.30.6.
La version d’OpenSSL avec laquelle le serveur est compilé (openssl version). Laissez vide pour utiliser 3.5.9, la branche à support à long terme.
Les groupes que votre version du serveur ne sait pas nommer sont omis ; les remarques ci-dessous expliquent pourquoi.
Indique aux navigateurs de n’utiliser que HTTPS pendant deux ans.
Utile seulement tant que votre AC exploite encore un répondeur OCSP.
L’échange de clés post-quantique est activé : cette configuration mentionne explicitement X25519MLKEM768.
# Généré par ecdsa.com d’après les recommandations TLSRef 6.0, profil intermédiaire : nginx 1.30.6 avec OpenSSL 3.5.9
# Options : HSTS
http {
server {
listen 443 ssl;
listen [::]:443 ssl;
http2 on;
ssl_certificate /path/to/signed_cert_plus_intermediates;
ssl_certificate_key /path/to/private_key;
# HTTP Strict Transport Security (63 072 000 secondes, nécessite ngx_http_headers_module)
add_header Strict-Transport-Security "max-age=63072000; includeSubDomains" always;
}
# Configuration du profil intermédiaire
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ecdh_curve X25519MLKEM768: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_ticket_key est une alternative au cache de sessions partagé
ssl_session_timeout 1d;
ssl_session_cache shared:MozSSL:10m; # environ 40 000 sessions
# Redirection du HTTP en clair vers HTTPS
server {
listen 80 default_server;
listen [::]:80 default_server;
return 308 https://$host$request_uri;
}
}
Ce que définit cette configuration
- Logiciel
- nginx · 1.30.6 · OpenSSL 3.5.9
- Protocoles
- TLSv1.2, TLSv1.3
- Suites de chiffrement TLS 1.3
- TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256
- Suites de chiffrement TLS 1.2
- 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
- Groupes d’échange de clés
- X25519MLKEM768, x25519, secp256r1, secp384r1
- HSTS
- max-age 63 072 000 secondes
- Agrafage OCSP
- désactivé
- Plus anciens clients compatibles
- Firefox 31.3.0, Android 4.4.2, Chrome 49, Edge 15 on Windows 10, IE 11 on Windows 10, Java 8u161, OpenSSL 1.0.1l, Opera 20, Safari 9
Remarques
- OKÉchange de clés post-quantique configuré : X25519MLKEM768.
- AvertissementAvec includeSubDomains, HSTS amène les navigateurs à refuser le HTTP en clair sur tous les sous-domaines pendant 63 072 000 secondes : assurez-vous qu’ils servent tous HTTPS avant le déploiement.
- InfoType de clé du certificat : ECDSA et RSA.
- InfoCourbes des certificats ECDSA : P-256 et P-384.
- InfoCertificats RSA : au moins 2 048 bits.
- InfoDurée de vie des certificats : 90 jours recommandés, 366 jours au maximum selon les recommandations.
- InfoPlus anciens clients compatibles : Firefox 31.3.0, Android 4.4.2, Chrome 49, Edge 15 on Windows 10, IE 11 on Windows 10, Java 8u161, OpenSSL 1.0.1l, Opera 20 et Safari 9.
Sources et licence
Les configurations suivent les recommandations TLSRef Server Side TLS 6.0 (5.8 pour le profil ancien) et la logique du TLS Configurator d’April King, Gene Wood, Julien Vehent, Glenn Strauss et de leurs contributeurs, successeur du SSL Configuration Generator de Mozilla. Les données des recommandations et le code porté du Configurator sont utilisés sous la Mozilla Public License 2.0 et conservés dans des fichiers distincts ; nos modifications du code porté sont publiées sous la même licence.
Les configurations Node.js, Java et .NET, ainsi que la configuration OpenSSL globale du système, sont rédigées par ecdsa.com selon les mêmes recommandations.
Where the settings come from
Every configuration on this page follows the TLSRef Server Side TLS guidelines, the community continuation of Mozilla's Server Side TLS guidelines. Guideline 6.0 defines two profiles. Modern allows TLS 1.3 only (RFC 9846, the 2026 revision of RFC 8446) and suits services whose clients are all from 2018 or later. Intermediate adds TLS 1.2 with forward-secret ECDHE and AEAD cipher suites only, and is the right default for almost every public server. The old profile, with TLS 1.0 and 1.1, was dropped in 6.0; the generator takes it from guideline 5.8, as the upstream TLS Configurator does, and says so in the output. TLS 1.0 and 1.1 have been deprecated since RFC 8996, so use the old profile only for clients that cannot do better.
The server templates are a port of the TLS Configurator, the successor of Mozilla's SSL Configuration Generator, covering 24 servers. Node.js, Java, .NET and the system-wide OpenSSL configuration are written by ecdsa.com on the same guidelines, which brings the total to 28. The guideline data and the ported code are licensed under the Mozilla Public License 2.0 and kept in separate files, as that license requires; the attribution under the tool links to both.
Why the version matters
A configuration must parse on the software that loads it. nginx learned http2 on in 1.25.1; Apache staples OCSP
only from 2.4.13; OpenSSL 3.0 refuses TLS 1.0 unless the security level is lowered to 0. The generator knows these
thresholds for every server, starts from the current release of each product, and adapts the output when you enter
an older version. A version that cannot do what the profile asks — the modern profile on a server without TLS 1.3,
say — produces an explanation instead of a configuration that would not start.
Post-quantum key exchange
Guideline 6.0 puts X25519MLKEM768 first in every profile. It is the hybrid of ML-KEM-768 and X25519 standardized in RFC 10024, and current browsers and CDNs negotiate it by default. A group list that names a group the software cannot parse makes many servers refuse to start, while a list that leaves it out silently turns post-quantum key exchange off. So the generator writes the group only where the version can name it: OpenSSL 3.5 for nginx, Apache, HAProxy and the other OpenSSL-based servers, Go 1.24 and Caddy 2.10, Traefik 3.5, JDK 27 for Java servers, Node.js 24.5 or 22.20. Where a server cannot name groups but its library offers the hybrid by default, the configuration keeps that default, and the result says which case applies. The "all hybrids" option adds SecP256r1MLKEM768 and SecP384r1MLKEM1024, built only from NIST-approved components, for servers that need them. How the hybrid works inside the handshake is shown step by step in the illustrated TLS 1.3 handshake and explained in X25519MLKEM768 explained.
HSTS and OCSP stapling
HSTS (RFC 6797) is on by default with a two-year
max-age and includeSubDomains, which makes browsers refuse plain HTTP on every subdomain; the notes remind you to
check that all of them serve HTTPS. OCSP stapling is off by default: since ballot
SC-063 publicly trusted CAs may stop running OCSP responders, and a certificate without an OCSP URL cannot be stapled.
The notes also carry the guideline's certificate advice and the maximum lifetime of public certificates on the day
you generate the configuration (CA/B Forum ballot SC-081) — see the
47-day certificate calculator for the full schedule.
Explain my config
The second tab reads an nginx or Apache httpd configuration you already run. It follows server blocks and virtual
hosts, applies inheritance from the http block or the server configuration, fills unset directives with the
defaults of your nginx or httpd version, and evaluates cipher strings the way OpenSSL 3 builds its list, so
HIGH:!aNULL turns into the exact suites a client may be offered. Findings are graded from critical (SSLv3,
compression, a stapling setup that keeps httpd from starting) to informational, each with its line number. Include
files are not followed: paste them too if they hold TLS settings.
What stays on your machine
Both modes run entirely in your browser; the page sends nothing anywhere. Configurations name the paths of the
certificate and key files, never their contents, and the explainer refuses a pasted private key. A share link puts
the settings — or the pasted configuration — after the # of the address, which browsers never send to a server.
The settings line inside a generated configuration is the same kind of link.
To see what your browser negotiates today, use the post-quantum browser check; to check deployed servers, the bulk domain checker. The differences between the protocol versions are compared in TLS 1.2 vs TLS 1.3 and X25519MLKEM768 vs X25519.