Open Cached · just now
80/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Nebraska, O=University of Nebraska Medical Center, CN=*.unmc.edu
Issuer
C=US, O=Internet2, CN=InCommon RSA Server CA 2
Valid From
February 19, 2025
Valid Until
February 19, 2026 80 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
E9:9D:0D:9B:8F:1D:40:46:C0:AB:2D:24:AC:04:4B:F5:C4:A9:73:49:88:50:09:6F:8B:72:69:93:AA:1A:34:56
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
Good
default-src; script-src; connect-src; +9 more
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
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
  • Strengthen CSP by removing 'unsafe-eval'
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • 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

Subject Alternative Names

1 domain