SSL check results of neon1.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for neon1.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

Report created Wed, 13 Jan 2021 18:13:29 +0000

The mailservers of neon1.net can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
neon1.net
2a02:200:3:1::100
10
supported
neon1.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
14 s
neon1.net
46.253.183.47
10
supported
neon1.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
14 s

Outgoing Mails

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

Certificates

First seen at:

CN=neon1.net

Certificate chain
  • neon1.net
    • 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)
  • neon1.net
Alternative Names
  • neon1.net
  • www.neon1.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-13
Not valid after
2021-04-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
93:35:CC:0E:44:05:A4:85:99:00:62:B5:A8:75:EA:22:ED:E7:F1:6F:5F:CC:BB:13:37:FD:60:67:DC:E1:03:17
SHA1
D8:B1:A0:1F:5A:36:54:70:B1:AC:00:C7:E5:B9:A2:D7:A5:D9:5C:47
X509v3 extensions
subjectKeyIdentifier
  • 7F:66:6D:BE:E9:88:F1:5D:B1:B3:0E:9A:90:81:C6:95:61:2A:26:06
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 : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Jan 13 17:55:31.942 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:37:36:90:61:A9:19:58:04:02:1E:66:23:
  • D2:59:72:48:76:6E:2D:48:D8:E3:59:CD:72:62:43:A2:
  • 63:C4:7D:F2:02:20:56:3F:DB:93:99:22:E6:CA:32:2B:
  • B3:1C:9D:9D:52:F2:DD:C3:A9:DA:6D:B7:0A:83:79:5B:
  • A5:A4:74:79:11:84
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Jan 13 17:55:31.901 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D7:A2:A4:90:9C:3A:B9:B5:8B:6C:6C:
  • 36:0F:D7:95:C2:21:AA:56:8E:B6:4D:50:15:71:51:0A:
  • 3E:C2:A7:E2:7A:02:21:00:D5:5C:71:07:AB:FD:9D:57:
  • FA:94:8F:70:4D:5B:7B:D9:38:4D:70:F7:A3:EF:F1:60:
  • 48:A0:F3:62:32:D6:BE:0F