Open
Cached
·
just now
88/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
339 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
Present
max-age=63072000; preload
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
amazon.com
digicert.com
; account=c2eb0f50ca113d7543d58a10f523d0469ff922f115e5e4e9056f3d5f87d3356c
Wildcard CAs
digicert.com
; account=c2eb0f50ca113d7543d58a10f523d0469ff922f115e5e4e9056f3d5f87d3356c
amazon.com
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
Subject Alternative Names
6 domains
atlassian.net
*.atlassian.net
atlassian.com
*.atlassian.com
jira.com
*.jira.com
Other domains in certificate