SSL check results of neobay.se

NEW You can also bulk check multiple servers.

Discover if the mail servers for neobay.se 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 Thu, 23 Sep 2021 00:43:58 +0000

We can not guarantee a secure connection to the mailservers of neobay.se!

Please contact the operator of neobay.se and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/neobay.se

Servers

Incoming Mails

These servers are responsible for incoming mails to @neobay.se addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.neobay.se
81.170.186.43
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail1.no-ip.com
8.23.224.50
20
supported
*.no-ip.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • SSL_RSA_EXPORT_WITH_RC4_40_MD5
  • TLSv1.0
  • SSLv3
5 s
mail2.no-ip.com
69.65.5.119
30
supported
*.no-ip.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.no-ip.com

Certificate chain
Subject
Common Name (CN)
  • *.no-ip.com
Alternative Names
  • *.no-ip.com
  • no-ip.com
Issuer
Country (C)
  • GB
State (ST)
  • Greater Manchester
Locality (L)
  • Salford
Organization (O)
  • Sectigo Limited
Common Name (CN)
  • Sectigo RSA Domain Validation Secure Server CA
validity period
Not valid before
2020-10-26
Not valid after
2021-10-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
72:19:D9:88:6F:FE:CD:2B:D7:EA:86:3E:B7:9F:D6:20:8D:52:92:64:75:FD:BD:56:B4:8D:DB:C6:6A:9D:6D:AE
SHA1
E0:40:9D:5C:9F:8D:1E:BA:75:34:F2:10:F1:65:D1:66:C4:1F:04:13
X509v3 extensions
authorityKeyIdentifier
  • keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
subjectKeyIdentifier
  • D3:EB:6C:70:85:71:3C:04:FD:6E:CB:17:C0:31:C3:21:F1:B7:F5:24
certificatePolicies
  • Policy: 1.3.6.1.4.1.6449.1.2.2.7
  • CPS: https://sectigo.com/CPS
  • Policy: 2.23.140.1.2.1
authorityInfoAccess
  • CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
  • OCSP - URI:http://ocsp.sectigo.com
ct_precert_scts
  • 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 : Oct 26 20:25:41.276 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:24:79:39:3B:A3:2A:77:A9:74:AC:7F:28:
  • C1:C0:62:B0:A5:97:3C:54:6C:DA:5C:13:E3:2C:B7:76:
  • 54:85:13:7F:02:21:00:C8:36:67:31:19:FF:01:20:42:
  • FB:4C:EB:60:40:8C:C1:9D:E4:82:25:5E:D7:32:E4:FE:
  • BF:C2:EE:6A:0F:50:E9
  • 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 : Oct 26 20:25:41.599 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E9:13:1E:C4:32:27:AD:10:0B:F2:19:
  • F0:F3:EC:0D:09:F3:61:CD:C4:22:B2:AE:28:60:F9:C5:
  • 83:6C:EE:F4:7C:02:21:00:84:18:B2:1E:02:15:3F:A7:
  • AB:7A:71:DC:AB:FA:F5:59:AB:D5:35:AD:BD:2E:7C:3B:
  • DE:BD:5C:D9:DE:BD:8D:00