Open
Cached
·
just now
82/100
SECURITY SCORE
Certificate Information
Subject
CN=serpact.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
December 15, 2025
Valid Until
March 15, 2026
50 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F5:08:11:69:81:BB:30:AD:CF:50:20:A9:4F:5F:A8:5C:AF:3A:75:92:11:84:CE:CC:53:EC:0D:7E:75:FF:97:03
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
Present
max-age=15552000; includeSubDomains
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Present
ALLOW-FROM SAMEORIGIN,ALLOW-FROM https://www.youtube.com,ALLOW-FROM https://public.slidesharecdn.com,ALLOW-FROM https://wa.slideshare.net/,ALLOW-FROM https://www.slideshare.net/,ALLOW-FROM https://serpact.com,ALLOW-FROM https://serpact.bg,ALLOW-FROM https://forms.monday.com
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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