Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
buildstream.co scored 90/100, demonstrating a strong security posture. No material issues found.
Critical gaps in: Security Headers. Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.
1 action item 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 buildstream.co compares
Grade distribution across 2378 companies we've scanned. buildstream.co scores better than 89% 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
buildstream.co — Grade A- (90/100)
2378 companies scanned
Security checks
Each check inspects a different part of buildstream.co's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 0/5 security headers present. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Known Breaches
No known breaches found in public disclosure databases.
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: 4 nameservers configured (ns-cloud-b4.googledomains.com., ns-cloud-b3.googledomains.com., ns-cloud-b2.googledomains.com., ns-cloud-b1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
Certificate Hygiene
Strengths: Certificate valid, 82 days remaining; Issued by Let's Encrypt.
Recommended actions
1 item
Steps to improve buildstream.co's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on buildstream.co: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://buildstream.co | 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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
SPF Record
Present
v=spf1 include:_spf.google.com ~all
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 82 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-b4.googledomains.com., ns-cloud-b3.googledomains.com., ns-cloud-b2.googledomains.com., ns-cloud-b1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.