SSL-Tools

SSL check results of ionos.laub.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for ionos.laub.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, 27 Apr 2024 09:25:25 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
ionos.laub.org
85.215.117.33
 -
supported
ionos.laub.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
ionos.laub.org
2a01:239:0:11f::1
 -
supported
ionos.laub.org
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 @ionos.laub.org address so far. Test mail delivery

Certificates

First seen at:

CN=ionos.laub.org

Certificate chain
  • ionos.laub.org
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • ionos.laub.org
Alternative Names
  • ionos.laub.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-30
Not valid after
2024-06-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6C:BF:1F:82:22:56:4C:77:0E:6D:33:89:FF:D4:27:E8:72:2C:3F:75:3E:83:F4:A9:F0:24:56:F8:E4:A7:B6:9F
SHA1
E9:5F:72:E3:89:90:48:DD:C8:FF:91:EC:BB:61:5D:EF:13:65:A9:81
X509v3 extensions
subjectKeyIdentifier
  • F2:EA:58:F4:4F:07:B0:0D:5B:01:9B:E1:E7:1A:7C:EF:37:F4:DC:2D
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 : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Mar 30 22:40:42.312 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0C:09:D4:CD:E9:4B:15:DA:69:12:14:0E:
  • 42:1C:E4:97:02:BD:88:AC:C7:A9:DF:C3:71:45:FC:1F:
  • 0D:D6:FE:26:02:20:2B:3F:7E:C1:BA:C1:75:BC:29:65:
  • 3E:AB:4D:50:F6:E0:21:88:B7:AA:7A:75:D3:9B:B0:0A:
  • 6B:AE:E4:40:92:C8
  • 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 30 22:40:42.409 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B0:EF:A5:85:93:A3:A3:D8:9F:65:65:
  • D0:C8:D4:C3:DA:55:1A:CB:3F:C0:0D:F3:5B:E0:0E:4D:
  • A2:4E:21:E9:6C:02:21:00:A8:DD:F1:E4:41:A9:94:24:
  • EA:8F:E4:2D:65:60:70:0E:5E:EE:A8:14:99:8F:C1:20:
  • BE:6F:C4:B1:EA:1D:FE:FF