Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=verkada.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
April 15, 2025
Valid Until
May 14, 2026
189 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
03:6D:76:FE:75:BA:F5:12:DF:0B:5D:01:ED:43:17:54:67:50:11:9F:EB:50:65:D9:03:49:07:4B:50:73:DF: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
Present
max-age=2592000
Content-Security-Policy
Weak
form-action; frame-ancestors
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
vibrate=(), geolocation=(), midi=(), notifications=(), push=(), sync-xhr=(), microphone=(), camera=(), magnetometer=(), gyroscope=(), speaker=(), vibrate=(), fullscreen=self
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • 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
9 domains
verkada.com
verkada.io
www.verkada.io
verkadacorp.com
www.verkadacorp.com
verkadagov.com
www.verkadagov.com
verkadamail.com
www.verkadamail.com
Other domains in certificate