SSL-Tools

SSL check results of neobee.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for neobee.net 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 Thu, 28 May 2020 15:02:23 +0000

The mailservers of neobee.net can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @neobee.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.neobee.net
77.105.32.188
 5
supported
mail-neobee.orion.rs
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
20 s
mx2.neobee.net
77.105.32.188
 10
supported
mail-neobee.orion.rs
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
20 s
mx3.neobee.net
77.105.32.188
 20
supported
mail-neobee.orion.rs
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
19 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail-neobee.orion.rs

Certificate chain
Subject
Common Name (CN)
  • mail-neobee.orion.rs
Alternative Names
  • imap.neobee.net
  • mail-neobee.orion.rs
  • mail.neobee.net
  • mx1.hosting.neobee.net
  • mx1.neobee.net
  • pop3.neobee.net
  • smtp.neobee.net
  • smtp1.neobee.net
  • smtp2.neobee.net
  • smtp3.neobee.net
  • webmail.neobee.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-12
Not valid after
2020-08-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F8:89:36:31:4A:12:60:DC:B4:24:1D:07:FA:35:CA:10:7C:D5:F2:E5:63:8B:82:7F:13:91:89:95:B1:CA:E8:B6
SHA1
C0:08:C8:D0:F8:AA:F3:48:31:19:EF:A2:55:4F:EB:38:1F:86:66:F0
X509v3 extensions
subjectKeyIdentifier
  • 31:27:8A:C4:30:DD:FD:65:FA:83:6F:FD:39:B0:0D:51:3B:04:8F:C1
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
  • 7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
  • Timestamp : May 12 02:38:25.723 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5C:2B:69:4D:90:F7:5D:66:67:22:C9:9C:
  • 87:CA:72:5C:B3:E4:8F:F8:51:61:95:AD:1F:42:53:F5:
  • A8:E4:0F:CF:02:21:00:C8:40:6A:78:68:D8:61:9B:2B:
  • 46:E5:E9:F0:90:11:3B:B9:5D:41:C5:1D:5C:FC:F0:96:
  • 5C:06:7A:D5:D5:63:67
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : May 12 02:38:25.700 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9B:01:7F:70:CA:ED:37:2A:DA:9A:98:
  • EA:0D:EC:43:4C:5A:BE:32:90:16:04:F6:66:D3:CD:4D:
  • 3D:4E:C5:50:27:02:21:00:88:62:74:9B:39:65:DB:0A:
  • 12:9D:43:84:A2:E2:96:4D:61:50:D0:8E:F3:9A:0C:8B:
  • 04:49:41:2C:1E:D2:6D:78