Cached · just now
92/100 SECURITY SCORE

Certificate Information

Subject
CN=*.kroo.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
January 10, 2026
Valid Until
February 08, 2027 286 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3C:7A:BA:E3:66:EE:22:3F:B8:58:B8:B4:71:73:18:0D:2F:47:8C:C1:18:BC:11:35:52:BA:41:52:F0:D3:01:58
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=31104000; includeSubDomains; preload
Content-Security-Policy
Good
connect-src; default-src; font-src; +8 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
fullscreen=(self "https://*.onfido.com" "https://sdk.onfido.com"), payment=(), sync-xhr=(); +7 more
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Strengthen CSP by removing 'unsafe-eval'

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