SSL check results of smtp.ibento.cz

NEW You can also bulk check multiple servers.

Discover if the mail servers for smtp.ibento.cz 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, 13 Jan 2021 22:19:54 +0000

The mailservers of smtp.ibento.cz can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @smtp.ibento.cz addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.ibento.cz
2a02:2b88:2:976::1
10
supported
alpha.ibento.cz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.ibento.cz
89.221.220.118
10
supported
alpha.ibento.cz
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 @smtp.ibento.cz address so far. Test mail delivery

Certificates

First seen at:

CN=alpha.ibento.cz

Certificate chain
  • alpha.ibento.cz
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • alpha.ibento.cz
Alternative Names
  • alpha.ibento.cz
  • ftp.ibento.cz
  • imap.ibento.cz
  • ispconfig.ibento.cz
  • mail.ibento.cz
  • pop3.ibento.cz
  • smtp.ibento.cz
  • webmail.ibento.cz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-10
Not valid after
2021-04-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AF:66:8C:A0:5A:84:60:F0:B2:3A:4C:90:D8:0D:ED:DE:39:BA:E6:50:D9:3B:35:E6:3F:2E:70:69:93:F2:C3:0A
SHA1
17:0C:53:36:1D:8F:5F:81:A2:4C:B7:F4:20:7F:A5:F2:9B:2D:30:E1
X509v3 extensions
subjectKeyIdentifier
  • A6:4F:86:EB:DC:EA:2C:4D:80:A5:1F:3F:DB:74:72:EE:C9:D3:68:F0
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Jan 10 22:48:14.660 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B3:32:C4:02:A7:88:25:42:DC:9F:D8:
  • 2E:1C:C8:F1:6D:9D:77:18:10:5F:88:9F:F9:8B:E5:7F:
  • AC:D4:DB:EE:31:02:21:00:97:A9:73:92:B0:8A:B5:74:
  • 04:EC:9A:30:88:91:5B:B8:97:3B:72:D2:73:B1:78:78:
  • 60:86:C2:1A:DE:BC:49:4E
  • 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 : Jan 10 22:48:14.691 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:43:CB:C0:3C:B8:E7:C8:D4:96:FA:7E:BD:
  • A5:82:E3:0D:59:42:70:7C:F4:BA:10:2B:D5:E0:42:05:
  • 78:C9:C4:22:02:21:00:9A:10:C8:28:92:7F:EB:87:AC:
  • D0:AC:0D:FA:6A:51:EB:C8:34:CF:DE:E7:FC:1A:0E:23:
  • EE:EA:A9:0E:FB:97:21