Open Cached · just now
85/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=CALIFORNIA, L=Santa Clara, O=Advanced Micro Devices, Inc., CN=amd.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=GeoTrust RSA CA 2018
Valid From
January 22, 2025
Valid Until
January 24, 2026 82 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
49:17:DB:32:C8:06:49:33:D2:88:CE:5F:60:82:29:D1:AB:DC:CE:77:75:1E:B6:14:7C:1E:9C:D5:E8:33:8B:3F
Alternative Names

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=31536000
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
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