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
85/100 SECURITY SCORE

Certificate Information

Subject
CN=*.spyrosoft.it
Issuer
C=PL, O=Unizeto Technologies S.A., OU=Certum Certification Authority, CN=Certum Domain Validation CA SHA2
Valid From
May 12, 2025
Valid Until
May 12, 2026 112 days
Public Key
RSA 3072 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C9:AD:FD:E4:4F:89:53:32:07:4E:92:80:3E:35:C2:C4:AE:AF:00:DE:5D:4A:4A:B2:07:3C:2A:A8:CE:76:68:1C
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
Excellent
max-age=31536000; includeSubDomains; preload
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
  • 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)
Wildcard CAs
Incident Reporting
CAA Issues
  • CRITICAL: Current certificate issuer 'C=PL, O=Unizeto Technologies S.A., OU=Certum Certification Authority, CN=Certum Domain Validation CA SHA2' is NOT authorized by CAA records. Authorized CAs: certum.pl, digicert.com, letsencrypt.org
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement

Subject Alternative Names

2 domains