Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Google Trust
Google AdSense
Ably
Google Tag Manager
G2
Google reCAPTCHA
Google Cloud Run
Amplitude
Reddit
Webflow
HubSpot Forms
Zapier
Cello
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Cloud Storage
Google Static File Front End
Google API JS Client
TikTok Analytics
Google Fonts
Twitter
Algolia
Hotjar
LinkedIn
ZoomInfo
Cloudflare Turnstile
Stripe
HubSpot Analytics
Google Search
Apple ID
Facebook
OneTrust
Rewardful
MNTN
Google Optimize
PostHog
HubSpot
Intercom
YouTube
Sentry
Google Cloud
Certificate Information
Subject
CN=veed.dev
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
February 23, 2026
Valid Until
May 24, 2026
41 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
32:79:82:5A:6C:0C:2B:E6:34:55:20:52:7C:2E:51:A9:99:83:A7:C5:DC:C5:AE:65:4E:0B:79:FA:86:3F:9B:10
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=15552000; includeSubDomains
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
pki.goog
; cansignhttpexchanges=yes
sectigo.com
ssl.com
comodoca.com
digicert.com
; cansignhttpexchanges=yes
letsencrypt.org
Wildcard CAs
comodoca.com
digicert.com
; cansignhttpexchanges=yes
letsencrypt.org
pki.goog
; cansignhttpexchanges=yes
ssl.com
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 6 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts