Open
Cached
·
just now
81/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=North Carolina, L=Raleigh, O=Red Hat, Inc., CN=subscription.rhsm.redhat.com
Issuer
C=US, ST=North Carolina, O=Red Hat, Inc., OU=Red Hat Network, CN=Red Hat Entitlement Operations Authority, [email protected]
Valid From
September 18, 2025
Valid Until
September 18, 2027
414 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C7:28:7B:04:26:26:78:0C:B3:E8:24:7C:89:58:54:C6:AB:9D:16:3A:53:6C:0F:51:22:A7:AC:86:62:05:76:47
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
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