DNS Gurus
Open Cached · just now
75/100 SECURITY SCORE

Certificate Information

Subject
C=DE, ST=Bayern, O=Friedrich-Alexander-Universität Erlangen-Nürnberg, CN=www.cms.rrze.uni-erlangen.de
Issuer
C=NL, O=GEANT Vereniging, CN=GEANT OV RSA CA 4
Valid From
December 05, 2024
Valid Until
December 05, 2025 13 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
EF:91:EF:6B:11:A4:1C:6D:0C:5A:83:FE:1C:96:07:9D:6F:80:1E:B3:A9:DC:9C:D7:0D:B7:0B:FD:97:B7:84:1D
Alternative Names
6 domains

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=15552000
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
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • 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