Open
Cached
·
just now
78/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=Pennsylvania, L=Pittsburgh, O=University of Pittsburgh-Pittsburgh Campus, CN=www.ccd.pitt.edu
Issuer
C=US, O=Internet2, CN=InCommon Intermediate CA - OVG2C
Valid From
October 23, 2026
Valid Until
January 20, 2027
81 days
Public Key
RSA
3072 bit
Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
E5:37:77:D5:58:3A:5C:15:13:C8:CC:09:F3:F4:9E:BE:39:84:8E:11:20:A1:E1:75:C7:5A:F9:69:4C:C6:AA:CA
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
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
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 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