DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Certificate Information

Subject
C=DE, ST=Bayern, O=Friedrich-Alexander-Universitaet Erlangen-Nuernberg, CN=apps.rrze.de
Issuer
C=GR, O=Hellenic Academic and Research Institutions CA, CN=GEANT TLS ECC 1
Valid From
November 03, 2025
Valid Until
November 03, 2026 313 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
BC:66:C5:E5:DF:D4:92:C8:0B:C4:D6:CC:29:26:A1:21:69:8C:07:D0:DE:7A:BF:0D:F8:EE:67:08:56:63:1A:EF
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=31536000
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(self),midi=(self),sync-xhr=(self),microphone=(self),camera=(self),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Significantly strengthen CSP directives

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