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

Certificate Information

Subject
C=IT, L=Firenze, O=Università degli Studi di Firenze, CN=st-umaform.unifi.it
Issuer
C=GR, O=Hellenic Academic and Research Institutions CA, CN=GEANT TLS RSA 1
Valid From
April 16, 2025
Valid Until
April 16, 2026 160 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E6:75:97:DC:AB:42:9E:93:D5:CC:C2:88:09:BC:15:2F:2E:04:85:C5:33:A9:46:F6:E2:78:E7:D6:0E:87:69:02
Alternative Names
10 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=15768000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
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 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