86/100 SECURITY SCORE

Certificate Information

Subject
CN=openam-broadridge-use4.id.forgerock.io
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
May 03, 2026
Valid Until
August 01, 2026 76 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B6:AE:49:6D:1A:9C:EF:15:24:23:98:3A:3A:68:89:7E:FC:AA:98:3C:51:05:56:D7:97:DA:17:C9:C7:C3:EA:16
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
Excellent
max-age=31536000; includeSubDomains; preload;
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Basic
frame-ancestors; script-src Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin
Permissions-Policy
Missing
Not configured
Recommendations
  • Add Content-Security-Policy header to prevent XSS attacks
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • 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

Subject Alternative Names

2 domains