Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Amplitude
Cloudinary
Cookiebot
Facebook
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
jsDelivr
LinkedIn
OptinMonster
Prismic
Typeform
unpkg
YouTube
Google Cloud
Certificate Information
Subject
CN=oribi.se
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
April 07, 2026
Valid Until
July 06, 2026
62 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
5E:33:45:92:D0:2B:BB:4E:13:EB:8B:A1:0D:14:81:DA:53:CE:DF:26:43:4A:F7:A8:A4:F4:F4:7B:4B:8B:BF:63
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=15552000
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Good
strict-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'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • 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