SSL-Tools

SSL check results of s4-2.jumu.hu

NEW You can also bulk check multiple servers.

Discover if the mail servers for s4-2.jumu.hu 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, 26 Apr 2026 00:30:23 +0000

The mailservers of s4-2.jumu.hu can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @s4-2.jumu.hu addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
s4-2.jumu.hu
217.113.62.31
 10
supported
jumu.hu
DANE
missing
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 @s4-2.jumu.hu address so far. Test mail delivery

Certificates

First seen at:

CN=jumu.hu

Certificate chain
  • jumu.hu
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • jumu.hu
Alternative Names
  • imap.jumu.hu
  • jerre.hu
  • jumu.hu
  • mail.jerre.hu
  • mail.jumu.hu
  • mail.zene.hu
  • pop3.jumu.hu
  • s1.jumu.hu
  • s2.jumu.hu
  • s3-2.jumu.hu
  • s3.jumu.hu
  • s4-2.jumu.hu
  • s4.jumu.hu
  • smtp.jumu.hu
  • wlh.hu
  • www.jumu.hu
  • www.wlh.hu
  • www.zene.hu
  • zene.hu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2026-04-22
Not valid after
2026-07-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
2D:BF:A1:C5:96:88:98:D3:A5:99:35:BF:F6:7C:FE:AA:C3:FA:03:C0:B9:65:64:4D:9D:91:7E:A9:18:FB:F5:E4
SHA1
DA:44:49:56:D2:A2:75:09:3D:7F:FF:F2:B7:8F:27:5C:3A:89:7B:D6
X509v3 extensions
subjectKeyIdentifier
  • 96:47:B3:6A:A0:D2:D3:FE:39:67:D2:3F:F3:78:54:49:39:85:15:AD
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/49.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : C2:31:7E:57:45:19:A3:45:EE:7F:38:DE:B2:90:41:EB:
  • C7:C2:21:5A:22:BF:7F:D5:B5:AD:76:9A:D9:0E:52:CD
  • Timestamp : Apr 22 11:17:44.849 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4A:F1:76:F4:51:28:32:5F:AC:93:DB:7B:
  • 03:51:45:17:5E:58:F6:F3:C7:80:A6:72:85:B3:63:8E:
  • 71:0A:14:96:02:20:33:29:BF:D1:CB:2C:98:FC:A2:F4:
  • 09:90:18:0A:26:A2:56:02:33:F4:A7:A8:79:24:CB:DD:
  • 0E:13:DB:C5:F6:74
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:8B:9D:6B:0F:FE:BF:81:B4:79:39:C6:D2:31:0A:86:
  • D6:D1:02:D4:F0:46:E2:18:2C:9D:E3:5F:5E:26:25:EF
  • Timestamp : Apr 22 11:17:45.700 2026 GMT
  • Extensions: 00:00:05:00:0B:2D:32:A0
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E0:E3:64:E6:8D:62:66:19:9C:3E:62:
  • E1:74:92:9B:B4:D1:4C:32:4F:18:93:5B:68:67:02:45:
  • DF:9E:3C:46:E0:02:20:61:13:5C:9B:AD:EE:90:89:63:
  • 01:F5:5C:AE:76:73:E2:74:6F:46:02:8F:BB:F4:57:1A:
  • F2:68:8A:FB:07:29:48