Cached · just now
91/100 SECURITY SCORE

Certificate Information

Subject
CN=theusfl.com
Issuer
C=US, O=Let's Encrypt, CN=YR2
Valid From
July 02, 2026
Valid Until
September 30, 2026 43 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
50:C9:3B:88:65:12:D2:C8:E9:29:EF:75:CB:CC:A1:28:5A:1B:79:D3:0D:EF:11:8B:94:7A:96:2E:DF:91:A1:8B
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
Present
max-age=28800
Content-Security-Policy
Basic
base-uri; font-src; form-action; +10 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Present
camera=(), display-capture=(), fullscreen=(self "https://*.youtube.com" "https://*.youtu.be" "https://video.wmt.media" "https://*.youtube-nocookie.com"); +3 more
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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