95/100 SECURITY SCORE

Certificate Information

Subject
CN=michaelmanagement.com
Issuer
C=US, O=SSL Corporation, CN=Cloudflare TLS Issuing ECC CA 3
Valid From
January 07, 2026
Valid Until
April 07, 2026 69 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
B8:A6:47:C3:21:20:A8:64:95:04:8E:EC:9E:64:BC:9B:F7:47:1C:D3:99:20:A8:F3:C6:59:7B:3E:08:D1:4B:31
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
Good
max-age=63072000;includeSubDomains
Content-Security-Policy
Strong
default-src; script-src; style-src; +6 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), bluetooth=(), compute-pressure=(), document-domain=(), encrypted-media=(), gamepad=(), gyroscope=(), hid=(), magnetometer=(), midi=(), screen-wake-lock=(), serial=(), speaker-selection=(), usb=(), xr-spatial-tracking=()
Recommendations
  • Consider adding 'preload' to HSTS for maximum security

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

2 domains