Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=*.atlassian.net
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
September 09, 2025
Valid Until
October 08, 2026
314 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1B:B9:FB:0C:F8:8A:11:DA:49:4C:DA:67:E7:28:24:81:30:1F:18:22:3E:48:56:BF:7D:78:E3:E8:46:55:96:68
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Basic
object-src; base-uri; script-src; +2 more
object-src 'self' blob:; base-uri 'self'; script-src 'report-sample' 'nonce-2d3db70704e74f1eb5d6720c7aee9f46' 'strict-dynamic' 'unsafe-eval' 'unsafe-inline' https:; frame-ancestors 'self'; report-uri https://web-security-reports.services.atlassian.com/csp-report/confluence-frontend
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
no-referrer, no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports
Subject Alternative Names
6 domains
atlassian.net
*.atlassian.net
atlassian.com
*.atlassian.com
jira.com
*.jira.com
Other domains in certificate