Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Google AdSense
Google Maps
Criteo
Google Tag Manager
Salesforce Cloud
Formulayt
Flourish
Google Translate
Reddit
Google DoubleClick
Google Analytics
Microsoft Advertising
6sense
New Relic
Google Static File Front End
Google API JS Client
Vidyard
Twitter
Hotjar
LinkedIn
ZoomInfo
unpkg
Turtl
Google Search
Adobe Marketo
Demandbase
Facebook
OneTrust
Salesforce Sites
AddToAny
Cloudflare CDNJS
Oracle Eloqua
jQuery
Visual Website Optimizer
YouTube
Microsoft Clarity
jsDelivr
Google Cloud
Certificate Information
Subject
CN=darts-ip.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 15, 2026
Valid Until
July 14, 2026
69 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0A:D6:EC:83:E2:81:80:95:F6:7C:5A:D5:AC:F8:94:31:AD:5F:3B:E0:B0:A9:26:36:C4:17:A3:D5:5D:34:EA:F2
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=31622400
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
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'
- • 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