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

Detected Technologies

See all in URL Inspect 3
AWS CloudFront logo AWS CloudFront AWS Certificate Manager logo AWS Certificate Manager Sentry logo Sentry

Certificate Information

Subject
CN=*.atlassian.net
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
July 16, 2026
Valid Until
January 29, 2027 195 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
01:22:B1:07:C6:D1:84:14:88:74:D0:B4:C7:90:32:03:F1:5D:A7:BD:28:86:3B:49:48:73:BE:52:57:65:94:BD
Alternative Names
60 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
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Weak
frame-ancestors; report-uri; report-to Analyze
Content-Security-Policy-Report-Only
AWS CloudFront logo
Basic
style-src; script-src; img-src Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Significantly strengthen CSP directives
  • • 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