SSL check results of dominik.fienko.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for dominik.fienko.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 Sun, 03 Mar 2024 17:32:20 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
server.fienko.de
2a03:4000:b:31b::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
server.fienko.de
46.38.251.19
10
supported
server.fienko.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=server.fienko.de

Certificate chain
  • server.fienko.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • server.fienko.de
Alternative Names
  • server.fienko.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-01
Not valid after
2024-05-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
54:96:B7:38:A1:86:B2:74:D9:5B:FB:51:EC:2C:BF:13:3E:2B:42:DC:0D:32:D6:92:A1:B9:FC:20:A3:48:E2:61
SHA1
BF:89:A3:64:70:87:80:AF:8C:60:9A:B4:9F:03:31:06:45:DF:60:C7
X509v3 extensions
subjectKeyIdentifier
  • 20:34:62:6C:1C:C8:4D:2E:E1:03:0A:7D:6B:CE:B7:CB:7B:39:2C:9C
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 : 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 1 02:41:21.573 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:93:43:80:72:8A:01:A1:AA:A8:BB:F4:
  • 0B:F3:52:ED:EB:C2:B6:F2:71:1E:0B:DE:57:D3:7F:C0:
  • 7C:0B:A8:4B:0F:02:20:6D:85:12:46:63:68:51:53:B9:
  • 96:86:CD:6B:52:9A:F9:75:B5:AD:21:3B:09:59:E3:66:
  • 56:89:0B:92:32:7E:ED
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 1 02:41:21.581 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B2:37:EB:2D:72:CC:B1:B7:65:9B:F2:
  • F3:74:02:A1:71:EA:48:9A:12:05:97:81:C2:A0:1A:22:
  • 17:88:C3:7A:48:02:21:00:E5:39:93:B6:C3:73:69:A7:
  • E9:09:D5:48:41:AE:A3:88:67:ED:D7:3C:17:07:60:C3:
  • EF:B9:DF:87:0D:F2:4F:57