Cached · just now
84/100 SECURITY SCORE

Certificate Information

Subject
CN=*.ctrader.com
Issuer
C=LV, L=Riga, O=GoGetSSL, CN=GoGetSSL RSA DV CA
Valid From
January 27, 2026
Valid Until
February 26, 2027 389 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
89:C1:25:7E:7A:16:CD:83:5F:28:71:22:92:24:76:F6:37:16:1F:21:45:61:48:B7:74:4D:FE:4B:29:5F:E9:48
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=31536000; includeSubDomains
Content-Security-Policy
Basic
default-src; frame-ancestors
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
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
  • 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
Configured (Restricts certificate issuance)
Current Issuer
Not Authorized (Potential misconfiguration)
CAA Issues
  • CRITICAL: Current certificate issuer 'C=LV, L=Riga, O=GoGetSSL, CN=GoGetSSL RSA DV CA' is NOT authorized by CAA records. Authorized CAs: comodoca.com, letsencrypt.org, sectigo.com, amazon.com
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • You have authorized 4 CAs - consider limiting to only the CAs you actively use
  • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts

Subject Alternative Names

2 domains