Open
Cached
·
just now
81/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
C=DE, ST=Bayern, L=München, O=Hochschule für angewandte Wissenschaften München, CN=sentry.hm.edu
Issuer
C=GR, O=Hellenic Academic and Research Institutions CA, CN=GEANT TLS ECC 1
Valid From
March 27, 2026
Valid Until
October 12, 2026
161 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
87:A2:CE:CC:B0:8E:69:73:11:FB:FC:EB:D6:AA:1C:CC:D2:B3:A9:3D:92:5D:E1:12:85:96:5E:14:29:B8:77:B7
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
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Present
nosniff;
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 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