Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
confluent.io scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, HSTS Header, Security Headers 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 confluent.io compares
Grade distribution across 2599 companies we've scanned. confluent.io scores better than 88% of them.
84
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
confluent.io — Grade A- (90/100)
2599 companies scanned
Security checks
Each check inspects a different part of confluent.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); DKIM configured (selectors: google, s1, s2, k1). Issues: No SPF record found.
DNS Configuration
Strengths: 4 nameservers configured (ns-238.awsdns-29.com., ns-697.awsdns-23.net., ns-1085.awsdns-07.org., ns-1943.awsdns-50.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
Detected technologies: Netlify. (Netlify detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 31 days remaining; Issued by Let's Encrypt.
Recommended actions
2 items
Steps to improve confluent.io's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for confluent.io but has gaps. Actions needed: add SPF record. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Verify with: nslookup -type=txt _dmarc.confluent.io
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for confluent.io can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .io TLD
4
Verify: dig +dnssec confluent.io
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); DKIM configured (selectors: google, s1, s2, k1). Issues: No SPF record found.
SPF Record
Missing
No SPF record found.
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 31 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-238.awsdns-29.com., ns-697.awsdns-23.net., ns-1085.awsdns-07.org., ns-1943.awsdns-50.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.