Cached · just now
96/100 SECURITY SCORE

Certificate Information

Subject
UNKNOWN=56686331, UNKNOWN={:asn1_OPENTYPE, <<19, 2, 78, 76>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, C=NL, ST=Noord-Holland, O=Entrust Netherlands B.V., CN=api.signhost.com
Issuer
C=CA, O=Entrust Limited, CN=Entrust EV TLS Issuing RSA CA 2
Valid From
May 26, 2025
Valid Until
May 26, 2026 130 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
31:7C:2B:70:40:FE:30:9F:9F:68:00:49:C5:B7:D5:9F:C9:6F:65:5B:52:7A:65:19:65:9A:AD:47:C8:70:15:30
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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Strong
script-src; base-uri; default-src; +4 more
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • 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

Subject Alternative Names

2 domains
api.signhost.com

Other domains in certificate

api.evidos.com