SSL-Tools

SSL check results of siedler3.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for siedler3.net 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 Thu, 25 May 2023 09:14:27 +0000

The mailservers of siedler3.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @siedler3.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.siedler3.net
2a03:4000:48:4fa::1
 10
supported
mail.siedler3.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.siedler3.net
45.132.247.244
 10
supported
mail.siedler3.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.siedler3.net

Certificate chain
  • mail.siedler3.net
    • 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.siedler3.net
Alternative Names
  • cloud.siedler3.net
  • mail.siedler3.net
  • www.siedler3.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-05-03
Not valid after
2023-08-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BD:64:29:D6:25:33:D5:AB:61:43:12:09:87:A5:1C:5C:1B:0A:CD:8D:EE:1A:8C:A8:EC:E1:81:6A:20:4A:44:68
SHA1
5B:21:1C:3C:BC:C9:D6:EC:E6:C4:06:40:1B:53:29:6D:78:5B:3B:FE
X509v3 extensions
subjectKeyIdentifier
  • 83:4C:C3:91:3A:BC:E7:79:5B:BB:B4:73:22:DA:AA:F1:D1:C6:6F:AF
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : May 3 15:46:13.993 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:EA:F9:18:4B:56:F1:83:5F:49:29:8F:
  • 20:BE:41:43:08:0B:CB:0B:03:7C:14:AB:6A:76:D7:1E:
  • 02:D5:D6:A6:41:02:20:5B:9B:13:CC:50:59:B5:82:F9:
  • 1F:0B:68:44:CC:F4:1C:30:BE:0D:90:D2:FA:17:1F:6E:
  • 2B:9F:01:09:B8:42:C2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
  • B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
  • Timestamp : May 3 15:46:14.076 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:60:E7:A2:20:73:DA:B7:1D:51:45:9B:ED:
  • 56:F3:12:66:93:7D:05:0C:6A:48:F1:77:07:5C:4B:25:
  • 8F:E8:B6:EA:02:20:65:16:F8:76:12:0A:F4:64:AC:D9:
  • 3F:C5:2C:2C:C1:4C:95:5A:37:CE:4E:E5:29:11:95:F1:
  • 97:AC:CD:80:89:CB