Open
Cached
·
just now
76/100
SECURITY SCORE
Certificate Information
Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 2, 85, 83>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 5, 84, 101, 120, 97, 115>>}, UNKNOWN={:asn1_OPENTYPE, <<12, 17, 71, 111, 118, 101, 114, 110, 109, 101, 110, 116, 32, 69, 110, 116, 105, 116, 121>>}, UNKNOWN=Government Entity, C=US, ST=Texas, L=Houston, O=University of Houston, CN=www.uh.edu
Issuer
C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2
Valid From
April 28, 2025
Valid Until
May 29, 2026
189 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
06:D7:88:B4:8D:9C:85:7C:55:4D:A3:AB:A6:93:E9:AA:35:91:3C:28:ED:52:7E:83:6D:94:8B:96:CF:96:EB:BB
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
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