SSL-Tools

SSL check results of akurz.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for akurz.net 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, 20 Apr 2024 07:39:48 +0000

The mailservers of akurz.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @akurz.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
email.evidentmedia.de
2a03:4000:6:b0ec::2578:bfec
 100
supported
email.evidentmedia.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
email.evidentmedia.de
37.120.191.236
 100
supported
email.evidentmedia.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=email.evidentmedia.de

Certificate chain
  • email.evidentmedia.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)
  • email.evidentmedia.de
Alternative Names
  • email.evidentmedia.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-18
Not valid after
2024-06-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7D:2A:FE:80:CF:13:4D:0D:ED:A1:00:F6:87:61:A8:9B:B9:16:B7:81:6C:EF:5D:2A:49:01:65:72:2B:A4:BC:A4
SHA1
34:A9:AC:B5:8A:0E:5F:6B:C5:04:97:E3:92:3A:9B:FC:05:CD:3F:76
X509v3 extensions
subjectKeyIdentifier
  • 92:69:DE:64:22:CA:75:ED:2A:CE:B6:60:3E:08:81:13:E2:F2:9E:88
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 : Mar 18 09:23:35.549 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:31:C8:EC:FA:DC:83:10:A8:E2:26:5C:E8:
  • 85:2C:AA:B4:03:37:6F:2C:47:7D:31:41:92:EF:B6:45:
  • D7:3C:3B:1C:02:20:30:9A:95:A4:33:2B:22:89:1A:8D:
  • EC:EA:3D:89:17:A2:E4:7F:CE:2A:A0:6E:AE:40:2F:0E:
  • 47:47:0A:C6:9E:B7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 18 09:23:35.549 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:11:3D:DE:E1:87:15:42:C6:CA:61:2B:2F:
  • 88:83:54:BB:E8:E6:F5:C7:AB:DB:79:A1:71:0B:01:3C:
  • 27:FA:E3:30:02:20:7C:92:02:B9:EB:B1:17:DA:9E:C4:
  • DD:89:30:FA:89:A9:B3:FB:4C:A0:26:22:7E:4E:07:C6:
  • 36:BF:65:AA:3D:22