Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
C=MC, ST=Monaco-Ville, O=NETEXCOM GROUPE INFORMATIQUE, CN=administro.fr
Issuer
C=GB, O=TBS Internet Ltd, CN=TBS RSA Organization Validation Secure Server CA 3
Valid From
February 03, 2026
Valid Until
March 06, 2027
299 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
41:F2:4B:EC:B7:BD:E0:1B:A7:8A:94:F1:FC:59:75:7D:15:C2:E1:C3:03:E7:CE:60:42:8C:7C:1E:FD:8E:A4:E2
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=86400
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
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
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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