Cached · just now
91/100 SECURITY SCORE

Certificate Information

Subject
CN=inriver.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
December 22, 2025
Valid Until
March 22, 2026 59 days
Public Key
RSA 3072 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1B:FF:A2:B7:C3:D1:C9:9D:9C:7E:B0:85:0F:75:98:33:C0:5C:BD:41:CB:9B:95:63:6C:1B:AB:C0:D0:E3:23:39
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=15768000; includeSubDomains
Content-Security-Policy
Basic
connect-src; default-src; font-src; +10 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
geolocation=self
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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