SSL-Tools

SSL check results of maxmazanec.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for maxmazanec.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

JSON Refresh

Report created Thu, 28 Mar 2024 13:55:48 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.it.nikomax.de
78.46.37.175
 10
supported
mail.it.nikomax.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.it.nikomax.de

Certificate chain
  • mail.it.nikomax.de
    • 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.it.nikomax.de
Alternative Names
  • autoconfig.maxmazanec.de
  • autoconfig.nikomax.de
  • autoconfig.servicedesk.it.nikomax.de
  • autodiscover.maxmazanec.de
  • autodiscover.nikomax.de
  • autodiscover.servicedesk.it.nikomax.de
  • mail.it.nikomax.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-10
Not valid after
2024-05-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5A:DE:02:F6:5B:BD:A0:3F:11:FC:AF:9F:B7:4E:EA:CE:D6:81:AE:EE:B2:21:8B:AE:36:B1:13:56:06:B8:18:FD
SHA1
C8:71:02:FB:DC:71:81:9F:E6:6F:B7:4E:FE:71:97:AC:0A:14:B6:5A
X509v3 extensions
subjectKeyIdentifier
  • A1:B0:59:C3:48:41:EA:AA:98:9E:17:CE:BA:96:05:C6:E3:AE:28:0D
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 : Feb 10 13:44:02.601 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:7C:92:55:53:0E:0E:F7:8E:18:B1:93:9F:
  • 30:4F:6D:3B:CA:F1:E0:A9:9D:57:54:47:94:85:CD:32:
  • 2C:92:EA:57:02:20:45:CB:BE:C7:63:BB:02:1A:7F:C2:
  • 2A:29:B2:00:70:58:C3:C3:2F:8E:69:75:28:CF:12:A1:
  • BD:13:3D:AB:B3:8F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Feb 10 13:44:02.687 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4F:74:97:32:30:04:09:BE:0A:A6:C1:D7:
  • B6:4D:FE:61:34:E4:8F:5E:9C:DA:3D:B3:D4:FA:CA:E6:
  • C5:79:6B:A1:02:20:1F:18:E6:07:4F:75:BF:DA:40:D0:
  • 52:36:64:B1:A3:CF:84:4E:29:26:F0:40:D8:86:35:EB:
  • 23:F9:72:56:F3:B0