Cached · just now
91/100 SECURITY SCORE

Certificate Information

Subject
CN=m2crowd.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 22, 2026
Valid Until
April 22, 2026 78 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F5:9D:F7:CF:FF:EB:EF:BF:98:D7:1B:1B:85:DB:4F:40:6E:0B:FD:81:48:A6:B5:AF:A0:3D:65:03:91:0E:BF:32
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=31536000
Content-Security-Policy
Basic
default-src; script-src; style-src; +5 more
X-Frame-Options
Present
ALLOW-FROM *
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
camera=(), fullscreen=(self), geolocation=(), microphone=(self), payment=()
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