SSL-Tools

SSL check results of pretalx.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for pretalx.com 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, 19 Jul 2026 00:31:41 +0000

The mailservers of pretalx.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @pretalx.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rixx.de
2a01:4f8:c17:763::2
 10
supported
mail.rixx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
mail.rixx.de
78.46.142.235
 10
supported
mail.rixx.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.rixx.de

Certificate chain
  • mail.rixx.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.rixx.de
Alternative Names
  • mail.rixx.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-07-07
Not valid after
2026-10-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
07:CD:41:34:9B:FE:D9:02:AE:3A:D2:09:45:9B:6D:14:64:D9:7D:92:28:E5:36:7D:D3:EE:AC:89:63:92:C9:46
SHA1
6B:D9:8E:81:E6:56:58:E8:57:B2:67:7C:8D:91:59:6F:4B:98:F0:EE
X509v3 extensions
subjectKeyIdentifier
  • A7:03:87:6C:2C:06:38:65:3B:FF:6D:EF:02:08:67:C9:FD:8E:6E:5E
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/29.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D8:09:55:3B:94:4F:7A:FF:C8:16:19:6F:94:4F:85:AB:
  • B0:F8:FC:5E:87:55:26:0F:15:D1:2E:72:BB:45:4B:14
  • Timestamp : Jul 7 15:51:10.121 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:EA:CA:84:12:0D:62:71:4C:A7:3E:FD:
  • BE:45:7B:51:E1:0C:07:CB:14:49:19:11:B3:84:76:9E:
  • EE:C5:77:D3:F1:02:20:5C:2B:3E:97:AE:A4:9D:84:C5:
  • E4:EC:DA:28:1C:74:91:BB:45:9C:AE:40:AF:48:3F:6F:
  • 11:8D:6C:FF:B7:6C:2B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6C:FE:50:19:43:A8:5E:A9:16:BC:52:D1:33:E4:DC:C9:
  • 1E:F1:41:1C:7D:25:84:20:D1:73:80:9E:18:18:EB:3A
  • Timestamp : Jul 7 15:51:10.363 2026 GMT
  • Extensions: 00:00:05:00:14:06:76:23
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1A:03:A6:F4:3D:35:5A:BD:D2:AE:F3:FC:
  • 75:22:87:5A:03:C2:B4:29:B5:64:84:64:EF:66:A5:90:
  • 3B:2D:56:F9:02:20:37:9F:20:5D:BA:34:C9:63:8E:F0:
  • 4B:AD:64:93:A3:CE:4F:B4:A1:A6:2E:06:F2:12:60:76:
  • BF:C6:C2:75:46:07