SSL-Tools

SSL check results of so36.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for so36.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 Mon, 25 May 2020 12:56:23 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
rage.so36.net
2001:678:a40:3000::81
Results incomplete
20
supported
rage.so36.net
DANE
not checked
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
rage.so36.net
192.68.11.81
Results incomplete
20
supported
rage.so36.net
DANE
not checked
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=rage.so36.net

Certificate chain
Subject
Common Name (CN)
  • rage.so36.net
Alternative Names
  • imap.mail36.net
  • imap.so36.net
  • mail.mail36.net
  • mail.so36.net
  • pop.mail36.net
  • pop.so36.net
  • pop3.mail36.net
  • pop3.so36.net
  • rage.so36.net
  • smtp.mail36.net
  • smtp.so36.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-03
Not valid after
2020-08-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DA:A5:85:84:A3:F9:92:7C:B7:05:5C:2D:51:82:66:4F:FF:56:76:B5:CA:F1:6F:08:54:84:F8:63:36:8F:85:8D
SHA1
C9:26:53:51:B9:AA:17:09:20:A5:EF:0C:35:A2:B0:62:A6:2C:FB:C9
X509v3 extensions
subjectKeyIdentifier
  • E8:C9:56:9A:75:7F:07:CA:A4:57:88:EF:43:A8:22:25:5F:7E:87:D7
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 : 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 : May 3 02:00:05.674 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:59:E1:49:EF:84:4E:D1:EB:F5:47:37:40:
  • 79:B7:60:49:DE:BD:54:8F:19:5F:AE:EB:23:2A:3B:C6:
  • 59:20:E0:FF:02:21:00:C7:F5:67:F6:48:20:6D:01:8B:
  • D9:3A:09:3A:66:BA:D5:5F:BC:BC:4E:35:A8:27:B5:F5:
  • 86:BA:5F:FB:34:5C:61
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
  • E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
  • Timestamp : May 3 02:00:05.671 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:66:05:29:A1:7D:9C:42:AB:A6:B0:3A:71:
  • B2:8C:F5:05:AB:27:CB:A9:3A:BC:48:D9:09:DA:14:A8:
  • 11:02:F6:F4:02:20:4A:DA:2B:56:EA:97:30:FB:23:7E:
  • 4B:0C:F8:CA:A4:03:D6:9D:CD:C8:98:25:B1:D2:45:F4:
  • F9:E9:A5:D2:B7:3A

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.rage.so36.net
  • DANE-TA: Trust Anchor Assertion
  • Use full certificate
  • SHA-256 Hash
valid
valid
_25._tcp.rage.so36.net
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid