SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Unknown Certificate Authority - the server's certificate is not trusted

Cached · just now
82/100 SECURITY SCORE

Certificate Information

Subject
CN=*.touk.pl
Issuer
C=PL, O=Asseco Data Systems S.A., CN=Certum DV TLS G2 R39 CA
Valid From
February 02, 2026
Valid Until
February 02, 2027 351 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
EA:AC:29:CE:FE:5A:62:91:B0:B5:D0:78:45:50:1C:D8:AD:10:05:58:73:25:92:BC:AA:CC:1C:39:63:91:46:DC
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
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Add Content-Security-Policy header to prevent XSS attacks
  • 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)
Authorized CAs
CAA Issues
  • CRITICAL: Current certificate issuer 'C=PL, O=Asseco Data Systems S.A., CN=Certum DV TLS G2 R39 CA' is NOT authorized by CAA records. Authorized CAs: certum.pl
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
  • Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

2 domains