Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Active incidents
YouTube
AppNexus (Xandr)
Cookie Information
Esri
Facebook
Google AdSense
Google Analytics
Google Cloud Storage
Google Conversion Tracking
Google DoubleClick
Google Optimize
Google Search
Google Static File Front End
Google Tag Manager
jsDelivr
Kaltura
LinkedIn
Microsoft Clarity
Pusher
Salesforce Sites
Siteimprove
Trustpilot
Twitter
Typeform
unpkg
Vimeo
Google Cloud
Certificate Information
Subject
CN=www.bring.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
March 27, 2026
Valid Until
June 25, 2026
45 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
11:1A:37:3F:8F:77:F0:33:D9:A4:2E:A9:0C:37:A5:A2:BB:90:3C:2E:AA:4D:01:19:59:B3:18:35:02:E5:E2:3D
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=31557600
X-Frame-Options
Excellent
DENY
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
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