Cached · just now
71/100 SECURITY SCORE

Certificate Information

Subject
L=Locality Name (eg, city), CN=192.168.1.1, UNKNOWN=Email Address, UNKNOWN={:asn1_OPENTYPE, <<19, 24, 65, 110, 32, 111, 112, 116, 105, 111, 110, 97, 108, 32, 99, 111, 109, 112, 97, 110, 121, 32, 110, 97, 109, 101>>}
Issuer
L=Locality Name (eg, city), CN=192.168.1.1, UNKNOWN=Email Address, UNKNOWN={:asn1_OPENTYPE, <<19, 24, 65, 110, 32, 111, 112, 116, 105, 111, 110, 97, 108, 32, 99, 111, 109, 112, 97, 110, 121, 32, 110, 97, 109, 101>>}
Valid From
May 10, 2022
Valid Until
May 09, 2032 2097 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
61:29:10:0A:A2:90:2E:B9:59:9D:3F:4D:E6:72:10:C8:46:80:E2:B6:D7:96:EF:35:46:EA:5B:D9:C9:27:D5:AE

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • TLS 1.3 is not supported (recommended)

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