Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Active incidents
PayPal
YouTube
Adyen
Arkose Labs
Brightcove
Cloudinary
Embedly
Active incidents
Google Analytics
Google DoubleClick
Google Pay
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Salesforce Cloud
Salesforce Sites
Stripe
Vidyard
Vimeo
Wistia
Google Cloud
Certificate Information
Subject
CN=support.dotloop.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
March 13, 2026
Valid Until
June 11, 2026
32 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
44:B8:AB:D9:EF:18:56:58:05:A2:BD:C5:EE:44:8F:51:39:59:84:83:95:16:E6:EC:C8:EF:19:53:7F:8B:96:D3
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=63072000; includeSubDomains
X-Frame-Options
Present
ALLOWALL
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • 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