Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
n8n.io scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, DMARC / Email Security, DNS Configuration all passed.
2 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How n8n.io compares
Grade distribution across 2519 companies we've scanned. n8n.io scores better than 89% of them.
79
A+
25
A
184
A-
190
B+
73
B
351
B-
121
C+
113
C
324
C-
117
D+
93
D
236
D-
613
F
n8n.io — Grade A- (90/100)
2519 companies scanned
Security checks
Each check inspects a different part of n8n.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DNS Configuration
Strengths: 2 nameservers configured (isla.ns.cloudflare.com., ernest.ns.cloudflare.com.); 6 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1, dkim).
Certificate Hygiene
Strengths: Certificate valid, 59 days remaining; Issued by Google Trust Services.
Recommended actions
2 items
Steps to improve n8n.io's security grade, ranked by impact.
1
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://n8n.io | grep -i strict
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add optional security headers (CSP, Permissions-Policy)
n8n.io has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://n8n.io | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1, dkim).
SPF Record
Present
v=spf1 include:_spf.google.com include:mailgun.org include:_spf.salesforce.com -all
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Valid
Strengths: Certificate valid, 59 days remaining; Issued by Google Trust Services.
DNSSEC
Enabled
Strengths: 2 nameservers configured (isla.ns.cloudflare.com., ernest.ns.cloudflare.com.); 6 MX records present; DNSSEC enabled; Zone transfers properly restricted.