Open
Cached
·
1h ago
88/100
SECURITY SCORE
Detected Technologies
Adobe Marketo
Algolia
Amazon Advertising
AWS
AWS Certificate Manager
Microsoft Advertising
CookieHub
Facebook
Google AdSense
Google Analytics
Google DoubleClick
Google Fonts
Google Search
Google Tag Manager
Hotjar
LinkedIn
Microsoft Clarity
New Relic
N.Rich
Optimizely
Quora
Reddit
TikTok Analytics
Twitter
YouTube
Google Cloud Storage
Certificate Information
Subject
CN=plugins.jetbrains.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
April 15, 2026
Valid Until
October 29, 2026
102 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
CB:98:EC:69:25:03:9C:4B:11:C3:9E:88:A0:3A:27:AC:41:92:42:42:38:48:BD:60:FB:59:BC:6B:65:0C:0E:4D
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=31536000 ; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
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
- • 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