Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Google Trust
AWS CloudFront
YouTube
Google AdSense
Google Tag Manager
G2
Spotify
AppNexus (Xandr)
Reddit
Webflow
HubSpot Forms
Zapier
Google DoubleClick
Google Analytics
Microsoft Advertising
6sense
Datadog
Oktopost
Google Fonts
Wistia
Twitter
Algolia
Osano
Hotjar
LinkedIn
Cloudflare Turnstile
HubSpot Analytics
Google Search
Lean Data
Qualified
PeerSpot
Storylane
Facebook
StackAdapt
GitHub
Builder.io
TechTarget
Akamai
HubSpot
Quora
Optimizely
Sentry
Certificate Information
Subject
CN=huntress.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 06, 2026
Valid Until
July 05, 2026
62 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
EF:43:01:97:0D:19:B0:EB:1F:CF:6B:A8:DF:AB:C7:E5:81:45:CC:DA:01:00:A2:17:87:BC:F8:F0:5E:55:CC:7E
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=63072000; includeSubDomains
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=(); +1 more
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
amazonaws.com
comodoca.com
digicert.com
; cansignhttpexchanges=yes
globalsign.com
letsencrypt.org
pki.goog
; cansignhttpexchanges=yes
ssl.com
Wildcard CAs
comodoca.com
digicert.com
; cansignhttpexchanges=yes
letsencrypt.org
pki.goog
; cansignhttpexchanges=yes
ssl.com
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 7 CAs - consider limiting to only the CAs you actively use