Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=go.infor.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
January 21, 2026
Valid Until
April 21, 2026
87 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
7D:C0:6A:C4:25:8C:BF:33:8A:E7:FB:17:DB:8A:DC:DC:22:3E:53:30:FF:08:62:A9:52:CB:D2:A8:E9:3A:51:42
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=31536000
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), browsing-topics=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
awstrust.com
digicert.com
letsencrypt.org
; validationmethods=http-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/23216805
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'issuewild' records to control wildcard certificate issuance