Cached · just now
82/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Minnesota, O=Mayo Foundation for Medical Education and Research, CN=mcc.mayo.edu
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R40
Valid From
July 09, 2026
Valid Until
January 23, 2027 168 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DC:83:90:8C:A1:59:BE:D8:5F:C2:1B:76:F0:7C:8D:B7:B0:92:0D:A6:EB:50:61:B1:13:89:17:11:6A:68:CD:23
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Basic
object-src; base-uri; script-src; +1 more Analyze
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Consider adding 'preload' to HSTS for maximum security
  • 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

Subject Alternative Names

1 domain