Cached · just now
92/100 SECURITY SCORE

Certificate Information

Subject
CN=envoke.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 24, 2025
Valid Until
February 22, 2026 55 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
CE:56:02:D5:A5:FC:0C:DE:B7:28:BB:B8:F2:65:14:3D:32:F0:2A:AE:C1:C7:6A:4C:B8:7C:96:F7:B2:CD:A7:DE
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=31536000; includeSubDomains
Content-Security-Policy
Basic
default-src; script-src; style-src; +10 more
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
autoplay=("https://player.vimeo.com"), camera=(), display-capture=(), fullscreen=(self "https://player.vimeo.com" "https://*.vimeocdn.com"), geolocation=*, microphone=(), picture-in-picture=("https://player.vimeo.com")
Recommendations
  • Consider adding 'preload' to HSTS for maximum security
  • 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