Open
Cached
·
just now
79/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=CA, L=San Fransisco, O=Postman Inc., CN=phs.getpostman.com, [email protected]
Issuer
C=US, ST=CA, L=San Fransisco, O=Postman Inc., CN=phs.getpostman.com, [email protected]
Valid From
February 07, 2019
Valid Until
February 04, 2029
1185 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DC:1C:1F:A0:6F:85:E7:15:90:6D:0A:A1:FF:9B:56:3F:44:D4:85:F4:A3:A2:DF:B3:38:13:EA:EF:78:1C:54:EE
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Not Authorized
(Potential misconfiguration)
Authorized CAs
CAA Issues
- • CRITICAL: Current certificate issuer 'C=US, ST=CA, L=San Fransisco, O=Postman Inc., CN=phs.getpostman.com, [email protected]' is NOT authorized by CAA records. Authorized CAs: letsencrypt.org
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance