Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
Google Trust
AWS CloudFront
Chili Piper
Google Tag Manager
Bing
G2
RudderStack
UnifyGTM
Netlify
Reddit
Midbound Cloud
HubSpot Forms
Google DoubleClick
Google Analytics
ClearBit
Iubenda
Google Static File Front End
Metadata.io
Google API JS Client
Wistia
Twitter
Hotjar
Kustomer
LinkedIn
Contentful
Influ2
Prismic
Stripe
HubSpot Analytics
Sequel
Google Search
Qualified
Facebook
Amazon S3
StackAdapt
Cloudflare CDNJS
SlideShare
Visual Website Optimizer
HubSpot
Vector
YouTube
Microsoft Clarity
jsDelivr
Google Cloud
Certificate Information
Subject
CN=profitwell.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 07, 2026
Valid Until
July 06, 2026
85 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
F8:C0:86:0B:3A:50:06:DA:7B:25:65:30:D1:CC:29:1E:90:0A:BC:BB:7C:E9:BB:61:89:73:57:5F:6E:69:04:9F
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
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Consider adding Permissions-Policy to control browser features
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