Cached · just now
88/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Illinois, L=Chicago, O=Syndigo LLC, CN=*.syndigo.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
December 03, 2025
Valid Until
December 18, 2026 268 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B6:20:FF:F2:AD:8A:92:9E:C8:78:7A:28:78:3B:B2:FA:93:22:9B:E1:ED:7A:21:B6:5B:2B:9E:1E:18:0D:B3:5D
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
Good
max-age=315360000; includeSubDomains
Content-Security-Policy
Basic
default-src; connect-src; script-src; +4 more Analyze
Content-Security-Policy-Report-Only
Basic
default-src; connect-src; script-src; +5 more Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
  • Consider adding 'preload' to HSTS for maximum security
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • 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

3 domains