Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Active incidents
Google Maps
Google Tag Manager
Bing
G2
PathFactory
Liveramp
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Tealium
Segment
Metadata.io
Google Fonts
Full Circle Insights
Wistia
Hotjar
LinkedIn
Drift
Cvent
TrustRadius
Google Search
BootstrapCDN
Figma
Adobe Marketo
Demandbase
Active incidents
Facebook
OneTrust
Cloudflare CDNJS
Intentsify
Visual Website Optimizer
TrustArc
Google Optimize
Akamai
Microsoft Clarity
Certificate Information
Subject
CN=targetprocess.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 03, 2026
Valid Until
July 02, 2026
54 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
45:5F:0A:F4:45:7A:9A:98:06:3E:CA:79:87:4A:88:24:5E:6B:CD:3C:C3:2C:32:72:9A:37:A8:75:FB:68:3E:AB
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
Excellent
max-age=31622400; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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