Free Cipher Suite Analysis
Free tool
Check your TLS cipher suites for weak algorithms, missing Perfect Forward Secrecy, and outdated TLS versions. Includes ready-to-paste Nginx, Apache, and Node configs.
- Cipher suite strength analysis
- Perfect Forward Secrecy validation
- Weak cipher detection
- TLS version compatibility check
No credit card requiredProduction-safe (100% passive)No setup or code required
Trusted by 4,500+ security & engineering teams
What you get for free
18 core security checks via this tool, passive scans, step-by-step remediation, security score on every result.
What Essential adds at $39/mo
+17 advanced checks, continuous monitoring, daily security score history, email alerts, GitHub SAST, board-ready PDFs, SOC 2 / ISO 27001 / PCI reports.
What are Cipher Suites?
Cipher suites are combinations of cryptographic algorithms used to establish secure connections. They determine encryption strength, key exchange methods, and message authentication. Modern cipher suites use AEAD (Authenticated Encryption with Associated Data) for optimal security and performance.
Perfect Forward Secrecy (PFS)
PFS ensures that past communications remain secure even if long-term private keys are compromised. Look for ECDHE (Elliptic Curve Diffie-Hellman Ephemeral) or DHE (Diffie-Hellman Ephemeral) in your cipher suite names to ensure PFS is enabled.
Cipher Suite Optimization
- Prioritize AEAD ciphers (AES-GCM, ChaCha20-Poly1305)
- Enable ECDHE for Perfect Forward Secrecy
- Disable weak ciphers (RC4, 3DES, CBC without proper padding)
- Use strong key exchange algorithms (ECDHE, DHE)
- Configure cipher suite order by strength
Modern Security Standards
- Preferred: TLS_AES_256_GCM_SHA384, TLS_AES_128_GCM_SHA256
- Acceptable: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- Avoid: RC4, 3DES, CBC mode without proper padding
- Deprecated: MD5, SHA-1 (except for HMAC in TLS 1.2)
What this analysis covers
- Supported cipher suites and their strength
- Perfect Forward Secrecy (PFS) validation
- Weak or deprecated cipher detection
- TLS version compatibility and preferences
- Key exchange algorithm analysis
- Encryption algorithm strength assessment
Implementation examples
Once you've identified the gap, applying the fix is straightforward. Here are the three configurations developers reach for most often.
Nginx
ssl_protocols TLSv1.2 TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_ciphers "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256";
ssl_ecdh_curve X25519:secp384r1;
ssl_session_cache shared:SSL:10m;
ssl_session_tickets off;Apache
SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
SSLHonorCipherOrder on
SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256
SSLOpenSSLConfCmd Curves X25519:secp384r1
SSLSessionTickets offNode.js (Express + Helmet)
import https from "node:https"
import fs from "node:fs"
import express from "express"
import helmet from "helmet"
const app = express()
app.use(helmet({ hsts: { maxAge: 31536000, includeSubDomains: true, preload: true } }))
https
.createServer(
{
key: fs.readFileSync("server.key"),
cert: fs.readFileSync("server.crt"),
minVersion: "TLSv1.2",
ciphers: [
"TLS_AES_256_GCM_SHA384",
"TLS_CHACHA20_POLY1305_SHA256",
"TLS_AES_128_GCM_SHA256",
"ECDHE-ECDSA-AES256-GCM-SHA384",
"ECDHE-RSA-AES256-GCM-SHA384",
"ECDHE-ECDSA-CHACHA20-POLY1305",
"ECDHE-RSA-CHACHA20-POLY1305",
].join(":"),
honorCipherOrder: true,
ecdhCurve: "X25519:secp384r1",
},
app,
)
.listen(443)Tool-specific questions
What's the difference between AES-128 and AES-256?
AES-256 provides stronger encryption than AES-128, but both are considered secure. AES-128 is often preferred for performance, while AES-256 is used for maximum security requirements.
Should I disable all CBC ciphers?
Not necessarily. While CBC ciphers can be vulnerable to padding oracle attacks if not properly implemented, they're acceptable when used with proper padding and in the right context.
What are AEAD ciphers?
AEAD (Authenticated Encryption with Associated Data) ciphers provide both encryption and authentication in a single operation, making them more secure and efficient than traditional ciphers.
How often should I review cipher suite configuration?
Regular reviews are recommended, especially after security updates or when new vulnerabilities are discovered. Use Barrion's continuous monitoring to track cipher suite changes over time.
Can I use different cipher suites for different TLS versions?
Yes, you can configure different cipher suites for different TLS versions. TLS 1.3 has a simplified cipher suite list, while TLS 1.2 offers more options but requires careful configuration.
Why Barrion
Built for the engineers who already have enough to fix.
Speed
Real-time results
Instant analysis with a detailed report. You see findings as the scan runs, not after.
Coverage
Comprehensive checks
35+ checks per scan covering TLS, headers, CORS, cookies, DNS, email auth, and more, in a single pass.
Action
Step-by-step fixes
Every finding ships with the exact remediation step for your framework. Hand it to the engineer who owns the surface.
Other tools
More free checks, for the rest of your surface.
Complete Security Scan
Complete website security analysis with comprehensive vulnerability detection
Pre-Pentest Security Scan
Passive scan that catches the misconfigurations a pentester finds first. Use it before a manual engagement to clear the easy issues.
Security Compliance Checker
Check compliance with PCI DSS, HIPAA, SOC 2, ISO 27001, and GDPR. Get compliance readiness reports.
WAF Checker
Detect Web Application Firewall presence through passive header analysis. Identify WAF/CDN providers.
Security Headers Test
Check your website's HTTP security headers configuration
TLS/SSL Security Checker
Validate your SSL/TLS configuration and certificate setup
FAQ
Frequently asked.
What is Barrion and how does it enhance website security?
Barrion is a security testing and monitoring platform for engineering teams, and it works in three ways. Passive scanning keeps a continuous, read-only watch over your live web apps and APIs. Codebase scanning connects to GitHub and checks your code for hard-coded secrets, insecure patterns and vulnerable dependencies. AI pentesting goes on the offensive, running agent-driven attacks that prove which vulnerabilities are genuinely exploitable. Every finding comes with a step-by-step fix you can ship right away.
How safe is Barrion to use for security testing?
Passive scanning and codebase scanning are completely safe to run, including against production. Passive scans only read your live app, so we never submit forms, brute-force endpoints or touch anything that changes state, and codebase scanning just reads your repository. AI pentesting is more aggressive by design, since its job is to confirm real exploits, so it runs rate-limited and non-destructive, and you agree the scope with us before it starts.
What types of security issues does Barrion identify?
It depends on the surface. On your live apps, Barrion catches misconfigurations across TLS and HTTPS, security headers, cookie flags, CORS policy, DNS records, email authentication (SPF, DKIM, DMARC), network exposure and the usual web hygiene gaps. In your codebase it finds secrets committed to the repo, insecure code patterns and vulnerable dependencies. AI pentesting surfaces the exploitable stuff, like SQL injection, cross-site scripting and broken access control, each one backed by proof it can actually be exploited.
What specific security checks does Barrion perform?
For live apps it checks TLS and HTTPS configuration, HTTP security headers, cookie flags, CORS policy, DNS and email authentication records, network exposure and common web hygiene issues. In your codebase it looks for hard-coded secrets, insecure patterns and vulnerable dependencies. AI pentesting takes it further by actively chaining requests to confirm exploitable flaws. Whatever the source, findings are ranked by severity and come with clear, step-by-step remediation.
What is Barrion's smart crawling?
Smart crawling automatically discovers the pages and endpoints of your app so scans cover the surface that matters, without you manually listing every URL.
How often does Barrion perform security scans?
You can run a scan manually whenever you want. Continuous monitoring of your live apps runs on its own (weekly and up on Essential, daily on Business), codebase scans can fire on every commit or pull request, and we alert you the moment something new shows up.
Is Barrion suitable for security testing of all business sizes?
Yes. Live-app monitoring, codebase scanning through GitHub and AI pentesting all work just as well for a solo developer as for a startup, a scale-up or an enterprise security team, without adding headcount.
How does Barrion handle data security and privacy during security testing?
Live-app and codebase scans are read-only by default, and we never store or expose sensitive data from your application. AI pentests are rate-limited and non-destructive, built to confirm whether something is exploitable without altering your data or affecting availability.
What if I'm not satisfied with Barrion's security testing service?
Paid plans start with a free trial, and you can cancel anytime. If something isn't right, contact us and we'll make it work for your team.
How does Barrion help with SOC 2, ISO 27001, NIS2, and other compliance frameworks?
Barrion produces audit-ready PDF and CSV reports suitable for SOC 2, ISO 27001, PCI DSS and NIS2, ready to share with auditors, customers and your board.
Anything else? Email contact@barrion.io.
Run a full report on your site.
Free first scan covers every check, no signup needed. Sign up to save the report and turn on continuous monitoring.