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

Certificate Information

Subject
C=US, ST=New York, L=New York, O=Ithaka Harbors, Inc., CN=jstor.org
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 OV TLS CA 2025 Q3
Valid From
July 30, 2025
Valid Until
August 31, 2026 295 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F8:A7:D1:31:33:C1:8B:FE:B7:D6:89:ED:2E:F6:83:08:4D:8B:8E:37:91:67:FF:48:3E:C3:41:E1:09:9C:BA:47
Alternative Names
40 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
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Content-Type-Options: nosniff
  • • 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