SSL-Tools

SSL check results of bamberger.it

NEW You can also bulk check multiple servers.

Discover if the mail servers for bamberger.it 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 Tue, 16 Apr 2024 19:21:50 +0000

The mailservers of bamberger.it can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @bamberger.it addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.bamberger.it
2001:16b8:bf9c:8c30:1e98:ecff:fe0f:cf94
 0
supported
smtp.bamberger.it
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
smtp.bamberger.it
83.135.209.208
 0
supported
smtp.bamberger.it
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=smtp.bamberger.it

Certificate chain
  • smtp.bamberger.it
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • smtp.bamberger.it
Alternative Names
  • asterix.bamberger.it
  • smtp.bamberger.it
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-26
Not valid after
2024-05-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
65:B5:3A:F8:15:47:06:1E:82:21:C5:D8:D7:A5:2B:1E:D7:1D:34:84:7F:7B:E0:89:55:56:CB:49:05:8E:81:87
SHA1
47:F2:68:C5:B8:34:75:48:55:29:52:78:71:3E:07:E1:E4:30:65:F5
X509v3 extensions
subjectKeyIdentifier
  • 46:01:FE:29:A0:90:D4:65:E4:86:81:B2:0E:73:FC:09:FF:BE:FA:DD
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Feb 26 04:07:01.162 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0C:94:29:CF:E7:72:CD:73:CE:37:FF:E3:
  • 35:FA:54:5F:14:BD:3A:A2:35:F3:9F:54:D3:E3:0B:BF:
  • 4C:AC:8F:5E:02:21:00:F1:A2:4C:35:C1:EC:B5:2B:58:
  • 18:CA:87:C4:5F:83:B9:5B:D2:7D:6D:8D:BF:7D:03:EF:
  • 06:8F:43:C8:50:45:49
  • 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 : Feb 26 04:07:01.665 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DA:CE:33:34:13:5C:5C:07:57:26:32:
  • FC:A1:67:71:39:20:87:AF:F7:57:0B:11:DB:9A:71:F8:
  • 41:D1:9B:BC:EF:02:20:2D:BB:57:01:94:0F:6E:C4:16:
  • C5:BF:F6:8A:C1:E4:13:52:E3:D5:CC:ED:4F:7C:26:0B:
  • E0:84:B6:50:00:9A:03