Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Google Trust
GitHub
Google AdSense
Google Tag Manager
Bing
Google Hosted Libraries
AppNexus (Xandr)
Zapier
Advertising.com
Trustpilot
Google DoubleClick
Google Analytics
ClickCease
Microsoft Advertising
Google Conversion Tracking
Imgix
Google Cloud Storage
Google Static File Front End
Google Fonts
Twitter
ChatSupport
LinkedIn
Tapfiliate
Google Search
Facebook
Instagram
Adobe Fonts (Typekit)
TikTok
Vercel
Smartlook
Rubicon Project
YouTube
Microsoft Clarity
Sentry
Google Cloud
Certificate Information
Subject
CN=testing.signmore.com
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
February 03, 2026
Valid Until
May 04, 2026
73 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
12:CE:3B:5A:E1:81:96:37:64:BF:46:A8:A0:3D:76:28:7D:FE:91:11:9A:F8:09:D4:84:4C:4F:7D:3B:7C:A0: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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • 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
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