DNS Gurus
Cached · just now
69/100 SECURITY SCORE

Certificate Information

Subject
CN=armytimes.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
November 06, 2025
Valid Until
December 04, 2026 315 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
43:09:B5:9A:A1:1E:29:48:CE:B9:E9:BF:AD:91:3C:68:BD:E3:2F:39:09:DA:A0:1A:56:73:8A:2C:04:68:D6:01
Alternative Names
6 domains

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)
  • • TLS 1.1 is deprecated and should be disabled
  • • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Weak
upgrade-insecure-requests
X-Frame-Options
Missing
Not configured
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
  • • Significantly strengthen CSP directives
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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