SSL check results of my-transporte.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for my-transporte.de 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

Report created Mon, 14 Sep 2026 08:09:25 +0000

The mailservers of my-transporte.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @my-transporte.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
hosting.wozi.net
2a01:4f8:221:3e90::ef:8
10
supported
hosting.wozi.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
hosting.wozi.net
46.4.12.178
10
supported
hosting.wozi.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

We have not received any emails from a @my-transporte.de address so far. Test mail delivery

Certificates

First seen at:

CN=hosting.wozi.net

Certificate chain
  • hosting.wozi.net
    • 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)
  • hosting.wozi.net
Alternative Names
  • hosting.wozi.net
  • www.hosting.wozi.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-08-19
Not valid after
2026-11-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
87:1D:76:FC:8E:42:05:EC:83:14:44:94:7F:AE:D1:60:98:43:4B:0F:EA:75:CF:4F:11:11:ED:F6:26:1A:7D:90
SHA1
AE:20:B1:79:A3:18:D3:6F:21:EE:21:96:9D:2C:99:3B:C6:B2:7F:5E
X509v3 extensions
subjectKeyIdentifier
  • 49:7E:3F:7F:96:A6:9B:99:EE:44:32:3F:8D:82:58:BB:9E:9C:C8:9F
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/81.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AF:67:88:3B:57:B0:4E:DD:8F:A6:D9:7E:F6:2E:A8:EB:
  • 81:0A:C7:71:60:F0:24:5E:55:D6:0C:2F:E7:85:87:3A
  • Timestamp : Aug 19 05:32:50.659 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:10:35:1D:AC:F6:85:C1:3C:28:DC:45:77:
  • 7C:54:4A:D6:54:F7:BE:23:C9:E8:81:D8:54:1A:96:49:
  • F7:55:56:FB:02:21:00:F9:5A:09:44:A8:E8:70:49:2E:
  • 16:67:33:D0:C0:B8:9F:2C:B9:CA:9E:F8:C0:D8:21:DA:
  • B0:00:ED:03:8C:EB:BB
  • 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 : Aug 19 05:32:50.992 2026 GMT
  • Extensions: 00:00:05:00:1F:E9:8E:0E
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FE:40:AA:BB:E5:AC:F5:C5:B7:A0:51:
  • 3F:E8:F4:C0:D0:4B:63:F7:AA:27:4D:30:2E:22:82:F2:
  • 01:A1:A8:BF:AB:02:20:3E:0D:C7:85:6C:0C:8B:37:DD:
  • 64:48:47:22:AD:34:29:9F:11:DC:7F:75:D5:89:2A:3B:
  • 24:1A:88:2B:12:BB:17