SSL check results of pmbi.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for pmbi.de 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

Report created Wed, 21 Jul 2021 12:38:16 +0000

The mailservers of pmbi.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @pmbi.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.pmbi.de
2a00:f820:490::20c:29ff:fe53:aaca
10
supported
mail.pmbi.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.pmbi.de
185.90.161.167
10
supported
mail.pmbi.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @pmbi.de sender addresses. Test mail delivery

Host TLS Version & Cipher
pmb-exchange.pmbremote.pmbi.de (185.90.161.167)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mail.pmbi.de

Certificate chain
  • mail.pmbi.de
    • remaining
    • 3072 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • mail.pmbi.de
Alternative Names
  • mail.pmbi.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-05-07
Not valid after
2021-08-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
48:30:08:61:CD:CE:9A:72:57:E1:A5:55:EB:9C:44:DB:63:8A:F2:93:FE:BD:B3:72:DC:95:A1:0F:88:A3:0F:49
SHA1
5D:7A:E5:97:05:D6:EC:7D:9A:20:C8:43:4C:45:1F:49:93:72:ED:43
X509v3 extensions
subjectKeyIdentifier
  • FA:1B:DC:9E:04:AF:94:C0:89:53:77:5D:87:4E:5D:EB:1B:84:FE:05
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : May 8 00:00:24.943 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:74:67:80:36:9A:56:2F:11:00:8A:20:06:
  • AD:65:A7:A5:72:BE:F2:73:17:D8:DD:08:12:7D:A2:04:
  • 68:82:BB:54:02:21:00:9E:22:81:56:55:B0:F4:DD:BF:
  • 06:B5:E4:16:1A:27:E2:99:B6:F9:BF:11:C9:0C:CE:50:
  • 3D:86:74:BA:81:5E:FB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : May 8 00:00:24.977 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A2:85:B4:7D:04:7B:3A:17:B9:B1:10:
  • 09:42:76:56:51:E4:02:1F:55:0D:90:3A:53:DC:C8:96:
  • FE:CB:54:7C:0A:02:21:00:AC:14:62:07:86:D7:5C:14:
  • 44:76:50:95:13:75:16:8D:F0:88:C5:23:42:7F:11:0C:
  • B5:15:CF:7E:7D:63:33:E6