DNS Gurus
Open Cached · just now
84/100 SECURITY SCORE

Certificate Information

Subject
CN=*.atlassian.net
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
July 10, 2025
Valid Until
August 08, 2026 277 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
20:2B:59:B3:DC:B6:97:D9:80:66:BB:CF:8A:C1:15:22:5C:17:DF:5D:BA:C0:B3:70:1D:F9:53:56:17:CB:57:FA
Alternative Names
45 domains

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
Not Authorized (Potential misconfiguration)
Authorized CAs
letsencrypt.org globalsign.com
CAA Issues
  • • CRITICAL: Current certificate issuer 'C=US, O=Amazon, CN=Amazon RSA 2048 M04' is NOT authorized by CAA records. Authorized CAs: letsencrypt.org, globalsign.com
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
  • • Consider adding 'issuewild' records to control wildcard certificate issuance