SSL-Tools

SSL check results of sggeneralblog.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for sggeneralblog.com can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

JSON Refresh

Report created Fri, 26 Apr 2024 19:09:35 +0000

The mailservers of sggeneralblog.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @sggeneralblog.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.sggeneralblog.com
23.106.50.5
 0
supported
sggeneralblog.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
14 s

Outgoing Mails

We have not received any emails from a @sggeneralblog.com address so far. Test mail delivery

Certificates

First seen at:

CN=sggeneralblog.com

Certificate chain
  • sggeneralblog.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • sggeneralblog.com
Alternative Names
  • *.sggeneralblog.com
  • sggeneralblog.com
  • sggeneralblog.com.tommykoh10.cldy.online
  • www.sggeneralblog.com.tommykoh10.cldy.online
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-28
Not valid after
2024-05-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9C:F1:C3:71:49:3F:FB:BA:52:0F:C6:AF:29:78:95:AB:41:84:04:5D:98:CB:68:D8:31:57:1B:FA:9F:87:C7:BE
SHA1
84:91:87:45:37:AA:E4:FB:2E:0A:95:5F:77:34:62:78:2D:14:40:35
X509v3 extensions
subjectKeyIdentifier
  • 12:0E:A1:CF:AE:F2:A1:3D:4A:24:7D:E0:65:F8:54:50:29:A7:2C:44
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Feb 28 12:35:17.674 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AD:72:7A:B0:06:7D:CC:33:60:6D:A1:
  • F6:AE:9B:DF:C8:52:26:A9:9F:F3:C6:BE:17:4C:B1:43:
  • CC:84:D4:30:02:02:21:00:FE:54:17:BB:E0:BB:FB:9D:
  • 28:A0:3C:48:65:20:6A:46:5B:EB:46:85:DB:91:F8:52:
  • B1:9C:37:55:64:B8:F1:53
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Feb 28 12:35:17.768 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:76:7A:9E:5C:3F:E8:B1:25:FE:F8:C2:3B:
  • B6:B1:B7:0F:47:82:F6:0F:28:F2:CF:9D:20:E0:A9:A9:
  • 99:BB:AF:C1:02:20:6B:2A:60:B3:20:F4:64:43:D8:FB:
  • 07:DA:63:CD:DE:36:DF:43:80:26:D9:5E:EF:19:66:18:
  • F2:84:A6:80:E2:4B