SSL-Tools

SSL check results of mailum.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for mailum.org 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 Sat, 20 Apr 2024 12:05:46 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mailum.org
2a0c:8900:1::40c7:27d3
 10
supported
mail.mailum.org
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s
mail.mailum.org
2.58.53.44
 10
supported
mail.mailum.org
DANE
valid
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 @mailum.org sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.mailum.org (167.86.81.43)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.mailum.org

Certificate chain
  • mail.mailum.org
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.mailum.org
Alternative Names
  • autoconfig.mailum.org
  • autodiscover.mailum.org
  • mail.mailum.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-03
Not valid after
2024-06-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B1:AB:85:F9:6D:4C:76:E6:52:66:EB:D6:D6:2A:72:83:2E:41:EA:56:6D:7E:E3:68:29:CE:DF:BC:79:60:91:48
SHA1
E8:53:E2:E3:47:01:6D:86:8C:91:95:17:2A:E6:63:42:6A:84:8E:75
X509v3 extensions
subjectKeyIdentifier
  • 03:41:F6:BA:75:81:D0:50:AA:7D:A6:CA:71:1F:39:BD:90:6E:6F:71
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 3 18:44:32.333 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3D:F0:3C:CC:D3:D3:6E:33:A9:23:F1:C3:
  • F7:D5:48:49:C1:9A:BF:1D:69:80:F9:9B:11:CF:FA:28:
  • 12:EE:A8:6A:02:20:29:36:DB:50:80:7F:BA:F0:0D:A4:
  • AB:6A:03:54:32:D5:81:0A:0A:E2:FE:0F:68:2E:A6:B3:
  • 1B:19:AB:22:D3:03
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 3 18:44:32.440 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CA:96:4F:02:F1:4F:78:77:2A:FF:17:
  • 53:73:36:19:DE:6E:E8:78:58:84:6E:8D:DD:4E:59:D6:
  • 5E:DD:0A:3F:04:02:21:00:F2:DB:23:13:25:64:36:B5:
  • F1:C2:D3:C3:35:B0:F1:3B:F8:17:7F:DC:05:E9:F8:C4:
  • 42:A9:99:40:FA:2E:20:94

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.mail.mailum.org
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid