Cached · just now
89/100 SECURITY SCORE

Certificate Information

Subject
C=FR, ST=Provence-Alpes-Côte d'Azur, L=Marseille, O=Institut de Recherche pour le Développement, CN=*.ird.fr
Issuer
C=GR, O=Hellenic Academic and Research Institutions CA, CN=GEANT TLS RSA 1
Valid From
October 08, 2025
Valid Until
October 08, 2026 78 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F0:10:60:DE:2B:A1:36:D4:F5:FE:66:87:F9:E1:4B:8B:1F:FF:49:2D:0A:B4:27:D7:3C:F1:3E:7B:8A:DA:32:51
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
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Strong
base-uri; child-src; connect-src; +13 more Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
interest-cohort=()
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Add Content-Security-Policy header to prevent XSS attacks

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

Subject Alternative Names

2 domains