SSL check results of mailpb.brekom.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mailpb.brekom.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 Fri, 19 Apr 2024 08:46:15 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mailpb.brekom.de
80.228.64.149
-
supported
mailpb.brekom.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @mailpb.brekom.de address so far. Test mail delivery

Certificates

First seen at:

CN=mailpb.brekom.de

Certificate chain
  • mailpb.brekom.de
    • remaining
    • 256 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mailpb.brekom.de
Alternative Names
  • mailpb.brekom.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-19
Not valid after
2024-07-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
19:03:76:6C:A8:D6:1A:A7:B7:EA:3C:A2:70:4A:B9:8B:03:04:59:26:7D:0E:45:ED:21:7D:AF:53:32:E1:1C:98
SHA1
12:7B:58:DA:F2:67:13:49:17:5B:65:35:07:B5:D5:CD:7A:77:D9:C2
X509v3 extensions
subjectKeyIdentifier
  • 03:57:5B:04:24:01:07:27:D8:E2:F3:10:88:FD:14:82:35:67:8D:08
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 : Apr 19 08:07:01.636 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:86:C1:E5:9B:32:75:4B:14:7A:76:E6:
  • 30:13:E7:0A:6B:8C:60:BF:32:94:44:7D:94:08:8E:8A:
  • 91:06:9E:96:6A:02:21:00:D7:C6:F4:46:5D:13:EF:09:
  • 75:C8:BE:74:8E:5A:B6:C5:07:5B:51:57:99:9F:3E:25:
  • 62:62:E3:97:22:49:7D:91
  • 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 : Apr 19 08:07:01.640 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:BE:5E:1B:9B:36:4A:52:7B:F3:92:DC:
  • 72:D7:54:37:26:70:EB:CB:CB:40:01:D9:EA:3D:0B:28:
  • 55:7D:8A:78:E9:02:21:00:FB:7A:54:A8:DD:CB:A5:7C:
  • 37:87:27:23:93:8E:01:36:0E:B0:AF:B9:A6:1C:5A:51:
  • 06:A1:31:DB:44:FD:13:63