85/100 SECURITY SCORE

Certificate Information

Subject
CN=accessgrantedsystems.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
January 14, 2026
Valid Until
April 14, 2026 86 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
D6:CA:0F:DC:96:4E:44:34:20:27:EA:EC:AA:17:40:78:8F:57:A1:32:72:60:63:5D:02:8C:E0:8D:2F:8D:0E:71
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
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(),midi=(),sync-xhr=(self "https://bookmenow.info" "https://book.mylimobiz.com"),microphone=(self "https://labs.heygen.com"),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self "https://embed.sequel.io"),payment=()
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Add Content-Security-Policy header to prevent XSS attacks
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking

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