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:

Hostname Mismatch - certificate is issued for infoload.rrze.uni-erlangen.de, web-prop.rrze.uni-erlangen.de, not for www.search.rrze.de

76/100 SECURITY SCORE

Certificate Information

Subject
C=DE, ST=Bayern, O=Friedrich-Alexander-Universitaet Erlangen-Nuernberg, CN=infoload.rrze.uni-erlangen.de
Issuer
C=GR, O=Hellenic Academic and Research Institutions CA, CN=GEANT TLS ECC 1
Valid From
September 16, 2025
Valid Until
September 16, 2026 268 days
Public Key
ECDSA 384 bit (P-384) Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
D5:CD:52:8F:FC:AD:CF:5A:24:38:CC:A3:10:E4:A3:3B:68:97:A7:5A:2B:3C:13:64:9E:EA:F3:0E:68:DF:85:08
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
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