SSL-Tools

SSL check results of nocomp.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for nocomp.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 Wed, 27 May 2020 06:56:12 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.nocomp.net
2001:985:d267:1:216:3eff:fe18:262a
 10
supported
mx.nocomp.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mx.nocomp.net
80.100.13.4
 10
supported
mx.nocomp.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
gtfomi.xs4all.nl
80.100.13.4
 10
supported
mx.nocomp.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx.nocomp.net

Certificate chain
Subject
Common Name (CN)
  • mx.nocomp.net
Alternative Names
  • gtfomi.xs4all.nl
  • mx.nocomp.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-04-05
Not valid after
2020-07-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D4:27:0A:68:73:F6:17:F1:4A:F9:85:B8:F6:8A:87:AD:96:77:DD:35:34:5B:5F:EB:02:BC:AA:ED:4D:61:86:65
SHA1
B3:AE:3C:54:45:C4:5D:80:1E:41:EF:39:81:74:0E:60:CD:7E:D5:5D
X509v3 extensions
subjectKeyIdentifier
  • 55:73:6B:B1:AE:38:8F:A8:C6:50:DA:A9:B4:C0:51:A1:6B:4E:23:93
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 : 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 : Apr 5 10:06:43.148 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E7:F9:44:9A:C4:A1:C2:55:6A:F2:83:
  • AA:1C:84:67:F4:52:B4:7D:40:7E:BD:B5:D6:13:95:38:
  • FE:7A:CF:5B:A9:02:21:00:A7:00:07:22:90:88:B6:06:
  • B2:07:74:1F:36:92:0C:C7:10:16:23:71:D5:B4:1E:27:
  • 91:51:72:A6:38:23:03:B8
  • 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 : Apr 5 10:06:43.193 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C7:FE:A1:F0:09:6A:BD:85:4C:FE:ED:
  • 4E:2E:E8:F6:D8:ED:5F:F6:69:62:51:7E:B0:D5:E0:F6:
  • 15:B1:CA:F1:2F:02:20:1E:2C:F3:0F:C6:AD:7C:27:A5:
  • 1F:8F:80:3E:D2:09:03:16:AF:74:A4:D6:E7:76:F5:5B:
  • D5:53:58:D2:CD:6C:F1