Cached · just now
92/100 SECURITY SCORE

Certificate Information

Subject
CN=creoline.net
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 28, 2025
Valid Until
February 26, 2026 60 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
FD:1E:26:3E:A1:90:D0:1A:8D:39:5C:77:C4:DC:F7:8D:E7:C4:02:94:9A:33:E0:DD:03:50:B7:44:0B:BA:75:94
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
Good
default-src; script-src; style-src; +10 more
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
geolocation=(),camera=(),microphone=(),payment=(),fullscreen=(self),usb=(),bluetooth=(),midi=(),magnetometer=(),gyroscope=(),accelerometer=(),clipboard-read=(self),clipboard-write=(self),gamepad=(),autoplay=(),web-share=(),screen-wake-lock=(),xr-spatial-tracking=()
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Strengthen CSP by removing 'unsafe-eval'

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