Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
bitbucket.org scored 92/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Cookie Security. Positive signals: MX Records & Mail Provider, DNS CAA Records, TLS 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 bitbucket.org compares
Grade distribution across 2378 companies we've scanned. bitbucket.org scores better than 92% 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
bitbucket.org — Grade A- (92/100)
2378 companies scanned
Security checks
Each check inspects a different part of bitbucket.org's public security setup. Green means healthy, yellow needs attention, red is a problem.
Cookie Security
Strengths: 3 cookie(s) analyzed. Issues: 2/3 cookie(s) missing Secure flag (atlCohort, ajs_anonymous_id); 3/3 cookie(s) missing HttpOnly flag (atlCohort, ajs_anonymous_id, bxp_gateway_request_id); 3/3 cookie(s) missing SameSite attribute (atlCohort, ajs_anonymous_id, bxp_gateway_request_id).
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS Configuration
Strengths: 4 nameservers configured (ns-584.awsdns-09.net., ns-1305.awsdns-35.org., ns-1746.awsdns-26.co.uk., ns-445.awsdns-55.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
MX Records & Mail Provider
Strengths: Mail handled by Proofpoint; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Proofpoint.
DNS CAA Records
Strengths: CAA records configured (7 record(s)); Authorized CAs: digicert.com, globalsign.com, letsencrypt.org, amazon.com; Violation reporting (iodef) configured.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
HSTS Header
HSTS enabled: max-age=63072000s (730 days) with includeSubDomains and preload. Meets best-practice configuration.
Known Breaches
No known breaches found in public disclosure databases.
security.txt (RFC 9116)
Strengths: security.txt found with 8 field(s); Contact: https://www.atlassian.com/trust/security/report-a-vulnerability, mailto:[email protected]; Expires in 331 days (2027-02-04T00:00:00.000Z); PGP signed (authenticity verifiable); Encryption key provided for secure reporting; Disclosure policy: https://www.atlassian.com/trust/security/report-a-vulnerability; Canonical URL specified; Preferred languages: en; Security hiring link included.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
CVE Exposure
Detected technologies: AtlassianEdge. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 174 days remaining; Issued by DigiCert Inc; 1173 certificates logged in CT; Certificates from 8 CAs: "GoDaddy.com, Amazon, COMODO CA Limited.
Recommended actions
2 items
Steps to improve bitbucket.org's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for bitbucket.org 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 .org TLD
4
Verify: dig +dnssec bitbucket.org
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 (Referrer-Policy, Permissions-Policy)
bitbucket.org has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://bitbucket.org | 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). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 ip4:167.89.90.3/32 ip4:167.89.37.79/32 ip4:167.89.38.16/32 ip4:167.89.38.188/32 ip4:167.89.38
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000s (730 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 174 days remaining; Issued by DigiCert Inc; 1173 certificates logged in CT; Certificates from 8 CAs: "GoDaddy.com, Amazon, COMODO CA Limited.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-584.awsdns-09.net., ns-1305.awsdns-35.org., ns-1746.awsdns-26.co.uk., ns-445.awsdns-55.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.