SSL-Tools

SSL check results of salzner.email

NEW You can also bulk check multiple servers.

Discover if the mail servers for salzner.email 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, 25 May 2025 00:32:29 +0000

The mailservers of salzner.email can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @salzner.email addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.salzner.email
2a12:edc0:4:b06e::1
 0
supported
mx.salzner.email
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
mx.salzner.email
45.145.224.109
 0
supported
mx.salzner.email
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx.salzner.email

Certificate chain
  • mx.salzner.email
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx.salzner.email
Alternative Names
  • autoconfig.salzner.email
  • autodiscover.salzner.email
  • mx.salzner.email
  • webmail.salzner.email
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-05-19
Not valid after
2025-08-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C2:D8:8A:B2:19:61:04:C2:9D:76:44:ED:90:6D:7D:B9:53:83:41:F4:74:8D:91:09:E7:4F:E8:08:51:AD:F8:0F
SHA1
53:2C:86:2A:EB:83:FD:EC:B5:07:85:DD:5F:DD:1B:44:E5:5B:06:BA
X509v3 extensions
subjectKeyIdentifier
  • 63:E5:C0:FA:50:05:38:D6:30:DA:66:EC:4F:47:F1:40:40:07:06:C3
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/15.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : May 19 10:22:15.577 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4D:47:31:00:D7:7A:1E:E6:A5:74:5F:3C:
  • 7C:9F:4B:91:78:C0:08:0C:61:2B:19:90:E5:A7:8A:99:
  • 9E:6E:D0:EA:02:20:17:C2:B4:40:5D:4A:F9:55:11:64:
  • 85:E8:E2:85:DB:9C:03:FE:F7:44:EC:E6:06:83:62:36:
  • 82:E2:48:BC:4D:FC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : May 19 10:22:17.572 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:5A:74:53:B8:9D:B2:8A:3A:C3:CB:ED:7D:
  • EA:B9:63:7E:51:FC:14:EC:02:95:40:34:A9:2A:5F:4D:
  • 92:07:20:B2:02:21:00:9F:26:BE:FF:D8:3E:D0:D6:C1:
  • CF:A9:DA:75:FC:7C:AA:FC:75:30:35:8D:7C:40:59:A6:
  • 1C:EA:2D:FF:44:B1:AF

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