SSL-Tools

SSL check results of email.nedcann.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for email.nedcann.com 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 Wed, 31 Jul 2024 00:30:26 +0000

The mailservers of email.nedcann.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @email.nedcann.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
email.nedcann.com
185.167.46.240
 -
supported
nedcann.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
email.nedcann.com
46.217.47.234
 -
supported
nedcann.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

We have not received any emails from a @email.nedcann.com address so far. Test mail delivery

Certificates

First seen at:

CN=nedcann.com

Certificate chain
  • nedcann.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • nedcann.com
Alternative Names
  • autodiscover.nedcann.com
  • download.email.nedcann.com
  • email.nedcann.com
  • nedcann.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-07-21
Not valid after
2024-10-19
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C1:48:19:63:6D:D3:47:31:B0:54:F8:32:D5:4D:72:0F:5C:60:72:82:5C:0B:A1:0E:99:8E:AE:F9:BD:25:BF:2E
SHA1
83:81:68:7D:7B:81:1A:00:98:48:A1:54:0E:9D:4C:41:C1:B6:83:35
X509v3 extensions
subjectKeyIdentifier
  • 51:2E:CA:D4:B1:DD:16:29:65:56:2C:B3:5A:04:11:6B:94:59:AA:C3
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.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 : Jul 21 07:23:55.073 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4E:40:71:EC:95:27:56:1A:7C:D0:55:27:
  • 98:51:C4:98:A4:DE:B0:2E:2F:AC:66:FE:56:9F:72:2F:
  • 97:31:92:E0:02:21:00:B5:23:23:0F:C3:6F:3C:FA:D4:
  • 4A:F2:52:F7:3D:58:7D:05:A0:0F:4C:3E:13:4C:2C:76:
  • A4:6C:5A:0D:5A:33:C2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Jul 21 07:23:55.064 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:67:7C:5F:19:B6:1F:AF:3E:C8:A0:04:E7:
  • 9C:1A:4D:11:22:36:14:97:32:CD:62:60:01:7A:C7:C8:
  • 84:7A:17:C2:02:21:00:BE:EB:FD:2D:0C:06:AD:F6:7B:
  • 98:67:CE:F6:F5:DB:73:5B:53:FB:72:84:6E:EE:FF:DD:
  • 39:26:4A:E3:F7:8E:49