SSL check results of taxi-kratzer.at

NEW You can also bulk check multiple servers.

Discover if the mail servers for taxi-kratzer.at 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 Tue, 09 Mar 2021 22:45:11 +0000

The mailservers of taxi-kratzer.at can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @taxi-kratzer.at addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail02.alpen.space
2a01:4f9:4a:356d::2
5
supported
mail02.alpen.space
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail02.alpen.space
95.217.120.2
5
supported
mail02.alpen.space
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 @taxi-kratzer.at address so far. Test mail delivery

Certificates

First seen at:

CN=mail02.alpen.space

Certificate chain
  • mail02.alpen.space
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • mail02.alpen.space
Alternative Names
  • autodiscover.alpen.space
  • autodiscover.angerer-spenglerei.at
  • autodiscover.markenstratege.com
  • autodiscover.wolfsteiner.tirol
  • cloud.alpenspace.eu
  • mail02.alpen.space
  • mail02.alpenspace.eu
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-02
Not valid after
2021-05-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FF:F9:C6:4B:15:62:93:AC:93:2A:A2:1E:43:CC:18:58:59:A9:CD:62:F7:08:53:D2:23:74:C8:42:AF:EB:4D:B6
SHA1
B3:7A:EA:8F:B7:F7:31:8E:7C:34:E8:AB:05:76:F8:6A:6F:CA:45:FB
X509v3 extensions
subjectKeyIdentifier
  • 6A:B0:2E:4C:02:66:4E:50:94:E8:D3:EB:23:A8:9F:87:6B:18:4D:7E
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Mar 2 07:44:50.753 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A6:57:76:CA:55:7B:DF:F3:B8:54:94:
  • 25:15:3D:B4:75:93:4A:3A:F7:32:30:EE:02:B5:8A:DF:
  • 61:88:B2:96:93:02:20:34:9A:91:AA:F4:B9:E8:A9:E2:
  • 16:CC:50:E4:51:0D:3D:FA:FB:19:66:7A:41:20:1F:DF:
  • 11:A3:9E:D4:39:7D:3C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Mar 2 07:44:50.756 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AF:D5:3F:7F:D4:51:7D:EE:CD:34:02:
  • E4:02:C3:1C:81:6D:7C:B8:BF:D9:7F:62:66:CC:A5:F0:
  • 6F:70:E6:2B:7E:02:21:00:EF:F5:D8:A5:62:51:0D:80:
  • B7:1C:9F:F3:0E:BD:2A:D2:6F:E9:81:86:01:31:C3:D6:
  • F4:09:7F:43:39:A8:C3:0B