Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Gravatar
AWS
AWS Certificate Manager
Microsoft Advertising
Cloudflare CDNJS
CookieYes
Facebook
Font Awesome
GitHub
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google reCAPTCHA
Google Search
Google Tag Manager
Hotjar
Knock AI
LaunchDarkly
LinkedIn
Microsoft Clarity
Quora
Reddit
Segment
Sentry
Twitter
YouTube
Zendesk
Certificate Information
Subject
CN=app.staging.codacy.org
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
July 02, 2025
Valid Until
July 30, 2026
102 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D4:FB:B6:DB:5A:ED:66:FA:CF:53:6C:A0:11:33:AF:EE:A1:DF:44:F0:CA:9F:F0:F6:09:F3:A8:53:32:AE:51:49
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=63072000; includeSubdomains; preload
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
geolocation=(self), microphone=(), camera=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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