Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
esm.sh
Let's Encrypt
YouTube
AppNexus (Xandr)
Bing
Cloudflare Web Analytics
Google AdSense
Google Analytics
Google DoubleClick
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Google Translate
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
LinkedIn
Microsoft Translator
6sense
Active incidents
Twitch
Google Cloud
Certificate Information
Subject
CN=sourceforge.net
Issuer
C=US, O=Let's Encrypt, CN=YE1
Valid From
August 12, 2026
Valid Until
November 10, 2026
86 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
F5:73:56:5B:E8:A4:3C:71:B0:89:04:5B:C3:6A:10:87:95:28:C2:3C:F9:EA:60:E1:08:61:8C:6C:65:C1:4B:54
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
Content-Security-Policy
Basic
upgrade-insecure-requests; form-action; fenced-frame-src; +5 more
Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
geolocation=(), microphone=(), camera=(); +4 more
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
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