Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
Gravatar
Adobe Marketo
Bing
Microsoft Advertising
Cloudflare CDNJS
Facebook
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Tag Manager
Hotjar
jQuery
jsDelivr
LinkedIn
Microsoft Clarity
Netlify
Securiti
Segment
Sentry
Slick Carousel
TrustArc
Wistia
Yoast
ZoomInfo
Certificate Information
Subject
CN=taxjar.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 10, 2026
Valid Until
July 09, 2026
66 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
37:DA:76:67:99:B9:8F:9B:9A:95:EF:99:F8:8C:37:5D:9B:3D:F6:61:A6:1F:74:EF:4B:80:2F:F8:1C:18:F4:F7
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
Weak
max-age= 31536000; includeSubDomains;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
geolocation=(), midi=(), sync-xhr=(); +6 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
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