Open
Cached
·
just now
93/100
SECURITY SCORE
Certificate Information
Subject
CN=api.tabsquare.ai
Issuer
C=US, O=Google Trust Services, CN=WR1
Valid From
November 28, 2025
Valid Until
February 26, 2026
41 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E8:E6:C9:CB:3C:97:23:96:92:07:61:BF:6B:C4:80:97:1B:C7:62:EB:4C:FD:C3:AF:1D:A7:0D:66:EE:80:92:6F
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
style-src; script-src; connect-src; +10 more
style-src 'self' 'unsafe-inline' fonts.googleapis.com; script-src 'self' 'unsafe-eval'; connect-src 'self' 'unsafe-eval' https: http:;img-src 'self' https: http: data:;default-src 'self';base-uri 'self';block-all-mixed-content;font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';object-src 'none';script-src-attr 'none';upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
midi=(), camera=(), geolocation=(), microphone=(), usb=(), microphone=(), accelerometer=(), xr-spatial-tracking=(), magnetometer=(), gyroscope=()
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