Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
bitrise.io scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Security Headers. Positive signals: Known Breaches, TLS Configuration, HSTS Header 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 bitrise.io compares
Grade distribution across 2378 companies we've scanned. bitrise.io 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
bitrise.io — Grade B- (80/100)
2378 companies scanned
Security checks
Each check inspects a different part of bitrise.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 1/5 security headers present. Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
DNS Configuration
Strengths: 2 nameservers configured (uma.ns.cloudflare.com., seth.ns.cloudflare.com.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google, mandrill, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
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, 82 days remaining; Issued by Google Trust Services.
Recommended actions
3 items
Steps to improve bitrise.io's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on bitrise.io: CSP, 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-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://bitrise.io | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Strengthen email authentication configuration
Email authentication is partially configured for bitrise.io 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.bitrise.io
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for bitrise.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 bitrise.io
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=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google, mandrill, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:_spf.google.com include:stspg-customer.com include:spf.mandrillapp.com include:amazon
Security Headers
1/5 present
Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 82 days remaining; Issued by Google Trust Services.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (uma.ns.cloudflare.com., seth.ns.cloudflare.com.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.