SSL check results of unse.edu.ar

NEW You can also bulk check multiple servers.

Discover if the mail servers for unse.edu.ar 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 Mon, 14 Jun 2021 07:01:21 +0000

The mailservers of unse.edu.ar can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @unse.edu.ar addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.unse.edu.ar
170.210.224.14
0
supported
smtp.unse.edu.ar
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s
mxb.unse.edu.ar
170.210.224.15
Results incomplete
1
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
mxc.unse.edu.ar
170.210.224.22
Results incomplete
2
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

We have not received any emails from a @unse.edu.ar address so far. Test mail delivery

Certificates

First seen at:

CN=smtp.unse.edu.ar

Certificate chain
  • smtp.unse.edu.ar
    • 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)
  • smtp.unse.edu.ar
Alternative Names
  • smtp.unse.edu.ar
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-12
Not valid after
2021-07-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3E:95:3D:5D:D7:AF:B2:8E:01:DA:59:84:90:BE:DB:D7:36:7A:6F:E6:BC:D6:A8:8F:05:BC:66:07:D0:E7:6C:67
SHA1
3F:96:74:00:C4:90:B9:12:B4:5A:31:83:6B:09:37:F3:E4:E2:72:5A
X509v3 extensions
subjectKeyIdentifier
  • C9:65:9B:26:15:89:CC:26:CF:53:5A:CC:65:A0:02:43:A6:10:CE:17
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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Apr 12 06:25:48.460 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:54:9E:5F:C3:DB:F7:EF:9C:BF:C1:13:71:
  • 8C:AC:63:82:82:BB:8F:E8:95:9E:46:89:6C:17:90:F2:
  • A8:5C:FD:6E:02:20:0C:C5:16:43:06:09:AC:85:EF:05:
  • 64:AE:96:0D:58:B4:B4:B5:14:8D:3C:F4:28:5F:75:A3:
  • 44:08:7F:09:F0:C2
  • 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 : Apr 12 06:25:48.594 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4D:DC:13:54:BD:06:AD:FA:4A:6D:9E:61:
  • 31:E2:2E:17:4D:1C:B3:22:B5:E5:85:8B:E0:48:49:AC:
  • 60:72:22:75:02:21:00:AC:13:06:0A:79:CD:38:DA:02:
  • 07:62:FE:6C:B7:BE:E7:DE:35:FF:E5:4F:D9:D5:96:5C:
  • E7:8B:B5:60:DF:C4:41