SSL-Tools

SSL check results of greenleft.org.au

NEW You can also bulk check multiple servers.

Discover if the mail servers for greenleft.org.au 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, 26 Apr 2024 09:42:42 +0000

The mailservers of greenleft.org.au can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @greenleft.org.au addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.greenleft.org.au
2400:8907::f03c:93ff:fedd:624f
 10
supported
mail.greenleft.org.au
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
20 s
mail.greenleft.org.au
194.195.252.13
 10
supported
mail.greenleft.org.au
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
20 s

Outgoing Mails

We have not received any emails from a @greenleft.org.au address so far. Test mail delivery

Certificates

First seen at:

CN=mail.greenleft.org.au

Certificate chain
  • mail.greenleft.org.au
    • 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.greenleft.org.au
Alternative Names
  • mail.greenleft.org.au
  • webmail.greenleft.org.au
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-23
Not valid after
2024-06-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FD:68:EE:99:C2:F2:B7:2D:61:32:9C:63:6D:96:E6:45:12:D9:08:1A:EF:BA:A4:A8:2E:E2:6B:18:78:22:5E:0E
SHA1
5B:B3:87:72:17:8E:DC:48:97:09:8E:61:75:C0:6D:6D:47:8B:52:FD
X509v3 extensions
subjectKeyIdentifier
  • 74:A7:8D:D1:76:AA:CF:60:86:50:9F:0A:A4:4F:79:ED:D5:75:2C:B3
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Mar 23 13:06:58.481 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0D:02:D1:EB:A9:5E:43:5D:E9:FC:74:D5:
  • DA:16:3A:E6:F1:7B:D2:1E:EF:40:06:7E:F1:83:ED:50:
  • 79:68:1B:50:02:20:77:2C:31:A0:08:2D:75:B2:48:35:
  • B4:87:D0:92:14:9E:F2:61:D7:8C:42:B3:4A:38:F1:90:
  • 03:A2:90:FB:69:5F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 23 13:07:00.493 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B7:DB:F6:89:96:EF:A2:64:B4:B6:47:
  • 54:BB:25:B6:61:ED:9F:09:BB:79:F3:34:35:61:3A:9B:
  • D5:09:2C:E9:4C:02:20:15:67:ED:A0:2C:CF:08:70:12:
  • 8F:45:3B:C5:8C:E0:F5:FF:57:5A:A2:C2:D7:91:2E:BB:
  • 4C:A9:D8:BC:75:EF:C0