Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Adobe Fonts (Typekit)
BootstrapCDN
Bugcrowd
Demandbase
Facebook
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
LinkedIn
OneTrust
Piwik PRO
Salesforce Pardot
6sense
Active incidents
SmartRecruiters
TikTok Analytics
YouTube
Google Cloud
Certificate Information
Subject
CN=imgarena.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 20, 2026
Valid Until
July 19, 2026
49 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
5B:75:EE:98:A5:B7:48:5C:13:87:29:61:02:0C:1B:07:21:E5:43:C3:36:BB:56:69:1B:30:AD:0B:EB:8D:63:BF
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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