Cached · just now
87/100 SECURITY SCORE

Detected Technologies

Certificate Information

Subject
C=FR, ST=Île-de-France, O=INGENICO TERMINALS, CN=ingenico.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV E36
Valid From
April 27, 2026
Valid Until
November 11, 2026 88 days
Public Key
ECDSA 384 bit (P-384) Strong
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
26:C8:30:E6:1B:BB:37:9A:E2:1B:1D:70:C0:2D:C9:52:25:E2:12:5B:BE:52:65:2A:19:93:0F:0E:D1:D3:9D:68
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
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-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