DNS Gurus
Cached · 1m ago
81/100 SECURITY SCORE

Certificate Information

Subject
C=DE, ST=Bayern, O=Friedrich-Alexander-Universitaet Erlangen-Nuernberg, CN=www.portfolio.rrze.fau.de
Issuer
C=GR, O=Hellenic Academic and Research Institutions CA, CN=GEANT TLS ECC 1
Valid From
December 19, 2025
Valid Until
December 19, 2026 363 days
Public Key
ECDSA 384 bit (P-384) Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
5D:53:0B:29:D9:3C:8F:BD:C7:D1:57:B9:9E:62:C2:39:DC:93:16:14:F7:07:68:D0:75:AC:87:2C:3A:8B:74:49
Alternative Names
18 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
Basic
default-src; script-src; style-src; +3 more
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
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • 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