DNS Gurus
Cached · 2h ago
80/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
AWS Certificate Manager logo AWS Certificate Manager

Certificate Information

Subject
CN=packages.atlassian.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
February 12, 2026
Valid Until
March 13, 2027 235 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
FD:9F:8E:3B:AA:B9:18:1C:6B:F3:9E:C1:A5:1B:28:7F:46:C5:76:89:49:6E:D9:3D:26:44:67:CF:C7:2B:E1:E3
Alternative Names
5 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
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
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
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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
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