SSL check results of autogassner.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for autogassner.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 Tue, 23 Apr 2024 14:11:40 +0000

The mailservers of autogassner.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @autogassner.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.autogassner.de
2a04:df80:30::45:153:179:229
10
supported
postfix.mail.autogassner.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.autogassner.de
45.153.179.229
10
supported
postfix.mail.autogassner.de
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 @autogassner.de address so far. Test mail delivery

Certificates

First seen at:

CN=postfix.mail.autogassner.de

Certificate chain
  • postfix.mail.autogassner.de
    • remaining
    • 384 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • postfix.mail.autogassner.de
Alternative Names
  • mail.autogassner.de
  • mail1.autogassner.de
  • postfix.mail.autogassner.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-15
Not valid after
2024-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BC:02:01:F6:8F:4A:C2:34:81:23:F0:6C:DD:6A:5E:1F:73:A3:63:D4:2A:F0:B3:7D:DA:FF:14:E4:49:9D:92:6B
SHA1
76:49:3F:FF:A9:D1:9E:57:B7:86:5B:60:B5:A8:A0:2B:5A:75:3B:09
X509v3 extensions
subjectKeyIdentifier
  • 53:6E:73:42:A6:22:E9:D6:4D:0F:E4:21:8A:58:F4:B4:D6:53:05:57
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 : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Apr 15 17:32:18.413 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E7:1D:93:4D:41:BF:BA:6E:54:03:BE:
  • 65:88:70:6B:5B:3D:B1:CD:D9:E9:21:75:70:7A:39:B1:
  • 9A:7B:44:52:0C:02:21:00:8A:6B:48:6F:1C:EE:B7:4C:
  • CA:57:E5:EB:47:F7:EB:B2:9F:67:73:CC:D5:3F:56:2A:
  • 08:1C:97:A3:95:21:CB:8A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 15 17:32:18.493 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7E:46:08:4A:94:65:4E:D8:91:91:CC:65:
  • 62:58:7F:F8:2E:BB:BE:62:71:5C:7D:52:A3:EA:D9:56:
  • B6:55:3A:61:02:20:7B:35:D5:01:AB:74:CB:05:74:BB:
  • F5:1E:71:13:FD:94:D0:65:9B:93:5D:79:A1:ED:E3:B5:
  • B8:A1:35:78:10:8F