Cached · just now
76/100 SECURITY SCORE

Detected Technologies

Certificate Information

Subject
CN=szaboandras.com
Issuer
C=AT, O=ZeroSSL GmbH, CN=ZeroSSL ECC DV SSL CA 2
Valid From
May 16, 2026
Valid Until
August 14, 2026 83 days
Public Key
ECDSA 384 bit (P-384) Strong
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
3F:7A:9A:C3:26:6D:53:BA:E4:82:61:59:B6:2C:E9:9E:52:8C:49:7E:DA:73:91:2D:4B:AA:96:18:28:60:47:03
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
Missing
Not configured
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Add Strict-Transport-Security header with max-age of at least 1 year
  • Add Content-Security-Policy header to prevent XSS attacks
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • Add X-Content-Type-Options: nosniff
  • 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
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

1 domain