SSL-Tools

SSL check results of pr0gramm.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for pr0gramm.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, 19 Apr 2024 18:21:51 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
post.pr0gramm.com
2a01:4f8:c0c:f5ed::1
 10
supported
*.pr0gramm.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
post.pr0gramm.com
116.203.241.171
 10
supported
*.pr0gramm.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.pr0gramm.com

Certificate chain
  • *.pr0gramm.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)
  • *.pr0gramm.com
Alternative Names
  • *.pr0gramm.com
  • *.staging.pr0gramm.com
  • pr0gramm.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-27
Not valid after
2024-06-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
86:36:8C:2D:AF:E8:31:EF:D5:E7:46:AA:10:7F:A0:6B:64:4C:18:BE:19:1F:B3:D2:C3:86:26:8F:60:EE:14:91
SHA1
7C:82:A8:A2:BB:AA:D5:00:A3:D1:EC:FE:D8:45:33:C6:B8:EB:AD:17
X509v3 extensions
subjectKeyIdentifier
  • 95:C1:3A:D5:D3:CF:71:FC:31:67:CC:47:4B:DA:A2:F5:9B:90:4B:83
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Mar 27 10:21:23.378 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:11:88:CB:7F:BF:D7:1F:A2:04:50:84:E3:
  • 37:DD:F5:90:54:4F:DE:1B:40:FC:CF:F0:B0:EB:29:5E:
  • BB:5D:2F:18:02:21:00:EC:F6:EB:92:4F:37:4B:6D:76:
  • EF:D6:A7:B2:AC:6B:B1:4F:83:15:D3:5F:30:70:4F:11:
  • BB:DD:71:37:1E:84:0C
  • 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 : Mar 27 10:21:23.416 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:88:B0:F9:FC:CE:57:8B:03:1B:4D:A5:
  • ED:66:EF:28:68:CC:65:8C:F4:85:CA:B8:73:65:9D:4C:
  • 3E:C5:10:13:00:02:20:5C:D6:4A:14:6A:66:2A:93:A2:
  • E6:1E:B1:27:4F:CF:F6:D8:68:B6:75:57:28:C2:DC:85:
  • 5B:02:A6:11:25:31:3F