SSL-Tools

SSL check results of neutrinet.be

NEW You can also bulk check multiple servers.

Discover if the mail servers for neutrinet.be 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 Fri, 07 Feb 2025 01:31:33 +0000

We can not guarantee a secure connection to the mailservers of neutrinet.be!

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

/mailservers/neutrinet.be

Servers

Incoming Mails

These servers are responsible for incoming mails to @neutrinet.be addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.neutri.net
2a01:4f8:c17:5d6d::1
 50
supported
mail.neutri.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
37 s
mail.neutri.net
116.203.253.98
Results incomplete
50
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.neutri.net

Certificate chain
  • mail.neutri.net
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.neutri.net
Alternative Names
  • mail.neutri.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-12-25
Not valid after
2025-03-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
48:DB:70:B5:9E:87:E6:CD:D2:B7:2A:3F:63:F0:76:AB:B5:47:FD:0E:EF:CB:19:FD:D6:AC:DA:4E:0F:17:64:A5
SHA1
D7:B8:A8:7F:CE:EC:8C:89:C1:3D:FA:0D:40:58:B9:1D:48:66:AF:2B
X509v3 extensions
subjectKeyIdentifier
  • 1A:C4:F3:A6:45:9A:AE:DE:AE:31:8D:DF:20:FB:19:A6:8C:25:75:62
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Dec 26 00:42:48.948 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4C:0D:42:84:23:45:08:36:FB:EA:4E:64:
  • 33:88:AC:55:EB:C7:17:43:9B:DE:AC:F2:40:31:1C:6C:
  • 06:D5:B4:41:02:20:6E:F9:FC:EF:F7:C0:F2:E1:AB:5D:
  • 7C:2A:08:81:13:D3:43:91:F5:97:74:B4:92:5C:95:DF:
  • E6:C9:5B:55:B2:E9
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Dec 26 00:42:48.946 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EC:D9:E8:4C:6E:FB:00:0C:C8:A8:7A:
  • EA:90:8F:1F:7D:57:6C:4A:90:58:83:72:61:B4:96:F8:
  • 2A:F8:75:61:EC:02:21:00:A5:FB:E5:D0:DB:DB:79:A3:
  • DB:7F:0B:58:10:26:EB:E2:1E:B7:24:9D:CE:D4:45:B2:
  • 9D:96:A0:A1:F0:01:93:5E