Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
influxdata.com scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, HSTS Header, Security Headers all passed.
3 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 influxdata.com compares
Grade distribution across 2378 companies we've scanned. influxdata.com scores better than 64% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
influxdata.com — Grade B- (80/100)
2378 companies scanned
Security checks
Each check inspects a different part of influxdata.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with hard-fail (-all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
DNS Configuration
Strengths: 4 nameservers configured (ns-127.awsdns-15.com., ns-2037.awsdns-62.co.uk., ns-820.awsdns-38.net., ns-1200.awsdns-22.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
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.
Certificate Hygiene
Strengths: Certificate valid, 176 days remaining; Issued by Amazon.
Recommended actions
3 items
Steps to improve influxdata.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for influxdata.com but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. 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
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.influxdata.com
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 influxdata.com 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 .com TLD
4
Verify: dig +dnssec influxdata.com
3
Upgrade to TLS 1.3
influxdata.com negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect influxdata.com:443 -tls1_3
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=none
Strengths: SPF record present with hard-fail (-all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:_spf.google.com include:_spf.salesforce.com include:mktomail.com a:zgateway.zuora.com
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 176 days remaining; Issued by Amazon.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-127.awsdns-15.com., ns-2037.awsdns-62.co.uk., ns-820.awsdns-38.net., ns-1200.awsdns-22.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.