SSL-Tools

SSL check results of ninakiel.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for ninakiel.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 Sat, 26 Sep 2026 00:30:12 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.ninakiel.de
2a01:4f8:fff2:a1:1::3
 20
supported
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mail.ninakiel.de
94.130.221.105
 20
supported
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 @ninakiel.de address so far. Test mail delivery

Certificates

First seen at:

Certificate chain
    • 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
Alternative Names
  • mail.danielmarohn.de
  • mail.littleroot.de
  • mail.ninakiel.de
  • IP Address:2A01:4F8:FFF2:A1:1:0:0:3
  • IP Address:94.130.221.105
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-09-25
Not valid after
2026-10-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
C5:84:48:3A:C9:55:01:99:7E:72:27:75:94:19:F8:15:74:A1:9B:ED:60:EB:B2:9F:7F:16:9E:29:5E:F1:28:B0
SHA1
83:10:1E:51:B6:E9:DA:4D:E3:78:84:63:79:56:76:9E:00:6A:A9:54
X509v3 extensions
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/115.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D7:6D:7D:10:D1:A7:F5:77:C2:C7:E9:5F:D7:00:BF:F9:
  • 82:C9:33:5A:65:E1:D0:B3:01:73:17:C0:C8:C5:69:77
  • Timestamp : Sep 25 01:07:21.113 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F1:8A:E6:46:F0:77:56:A1:03:D6:12:
  • E6:1B:DD:B1:9C:6F:A4:8C:94:B0:9E:10:1A:90:C2:34:
  • 0A:B5:54:2A:D2:02:21:00:93:CA:EA:12:18:C2:77:AF:
  • C3:84:23:74:0A:E6:DB:33:5F:17:E0:25:22:2C:D0:6F:
  • ED:4E:12:B1:C0:A7:CB:C2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A8:26:CB:E3:0A:C6:35:12:46:53:3F:E0:65:F1:4F:19:
  • D9:6E:19:08:13:C4:1D:D9:6D:79:00:B3:12:3C:55:27
  • Timestamp : Sep 25 01:07:21.444 2026 GMT
  • Extensions: 00:00:05:00:37:2A:DB:6D
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:83:A8:AE:E3:C2:55:1D:17:63:C7:6B:
  • 9F:18:D1:FB:E3:15:80:EA:3E:1B:BA:06:23:62:BD:95:
  • C6:E6:B3:C0:F6:02:20:3F:ED:DC:C7:D2:1C:AF:43:44:
  • 77:F8:4F:2B:55:8A:54:A3:4A:54:1E:37:F5:77:EA:50:
  • C2:3B:6E:56:8A:59:4E