SSL-Tools

SSL check results of inscomers.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for inscomers.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 Sun, 21 Apr 2024 22:40:47 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail-in01.role.inscomers.net
2a01:4f8:10b:144d::e417
 10
supported
mail-in01.role.inscomers.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
4 s
mail-in01.role.inscomers.net
94.130.16.13
 10
supported
mail-in01.role.inscomers.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

We have received emails from these servers with @inscomers.net sender addresses. Test mail delivery

Host TLS Version & Cipher
m1.inscomers.net (IPv6:2a01:4f8:222:2c03::4)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail-in01.role.inscomers.net

Certificate chain
  • mail-in01.role.inscomers.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail-in01.role.inscomers.net
Alternative Names
  • m1.inscomers.net
  • mail-in01.role.inscomers.net
  • mail-out01.role.inscomers.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-21
Not valid after
2024-07-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EC:87:67:58:25:CB:D2:83:A9:A0:88:D7:A7:AD:C8:9E:A9:99:20:0B:57:F0:E6:9B:02:90:60:2F:FF:79:F5:CF
SHA1
F4:A1:C9:9E:3E:57:6E:8B:61:A8:6B:5B:D6:6F:D1:C7:C6:F0:BF:44
X509v3 extensions
subjectKeyIdentifier
  • 84:A1:CD:63:0F:5E:41:CC:E7:11:49:E8:AE:4B:2E:7D:E1:36:08:34
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 21 22:39:15.093 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:38:1E:FB:64:2B:F6:9A:CF:1C:3E:80:95:
  • E1:CD:F9:F3:3E:06:38:D0:60:10:28:EA:61:D1:59:44:
  • CA:C8:C5:59:02:20:36:1D:26:C6:D6:13:83:78:16:55:
  • 79:22:50:FB:E3:08:67:74:05:0E:EC:E7:A7:DC:0B:BF:
  • 8A:11:AB:B2:D0:46
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 21 22:39:15.122 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8D:FF:29:6B:97:91:F9:9E:C8:F8:B8:
  • 09:11:A5:5D:CA:6D:3E:E8:6A:17:5B:27:8D:A8:74:F7:
  • 61:3B:1E:7C:4D:02:20:15:24:2C:9E:D7:D2:8D:B1:D3:
  • 14:08:BD:A2:29:55:1C:A1:82:29:D9:4A:22:F1:98:8C:
  • A1:84:33:FE:4A:EA:3D