Open
Cached
·
33m ago
83/100
SECURITY SCORE
Detected Technologies
UserWay
PayPal
Google AdSense
Google Maps
Quantum Metric
Google Tag Manager
Bing
GoDaddy
Amplitude
Braintree
Fullstory
Google Translate
Reddit
hCaptcha
Yahoo
HubSpot Forms
Cookiebot
Google DoubleClick
AdRoll
Google Pay
Google Analytics
ClickCease
Microsoft Advertising
Iubenda
Mixpanel
Square
Google Cloud Storage
Google Static File Front End
LaunchDarkly
Google API JS Client
TikTok Analytics
Leadfeeder
Google Fonts
Marqeta
Active incidents
Twitter
Quantcast
Bunny Fonts
Stape
Hotjar
LinkedIn
Klaviyo
Contentsquare
Stripe
Google Search
Yandex
Apple Pay
Facebook
Instagram
Amazon S3
StackAdapt
Lucky Orange
Snapchat
Adobe Fonts (Typekit)
Pinterest
TikTok
Smartlook
Taboola
IP-API
ConsentManager
ipify
Tawk.to
HubSpot
YouTube
The Trade Desk
Microsoft Clarity
Sentry
jsDelivr
Google Cloud
Certificate Information
Subject
C=US, ST=Oregon, L=Portland, O=Full Creative, CN=*.setmore.com
Issuer
C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Valid From
December 08, 2025
Valid Until
December 08, 2026
248 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1B:3C:F0:05:74:93:A6:46:B2:B2:9A:1B:F5:D5:38:D0:3A:41:D7:64:77:EF:D1:C6:81:F2:AC:0E:94:CD:29:37
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
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(self)
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • 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
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