SSL-Tools

SSL check results of blueline-networks.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for blueline-networks.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, 07 Mar 2024 18:51:32 +0000

The mailservers of blueline-networks.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @blueline-networks.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.blueline-networks.de
81.169.172.246
 15
supported
mail.blueline-networks.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.blueline-networks.de

Certificate chain
  • mail.blueline-networks.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)
  • mail.blueline-networks.de
Alternative Names
  • *.mail.blueline-networks.de
  • mail.blueline-networks.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-07
Not valid after
2024-06-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
4C:1C:01:12:0B:1F:A6:69:4C:5D:C3:A0:7D:EC:F2:0B:21:D3:6E:48:9A:AD:65:BA:3A:D1:23:24:1C:EC:1D:DC
SHA1
D8:4F:28:79:46:32:5A:27:DB:A3:36:19:3F:45:72:44:92:AD:99:F7
X509v3 extensions
subjectKeyIdentifier
  • 78:7B:DD:2D:76:36:7D:9B:0D:B6:E3:5F:0B:E9:E7:DE:FC:83:F2:2C
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 7 18:16:31.427 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AC:9B:D7:75:D1:7F:C4:9A:3C:AE:C5:
  • 08:19:BB:A0:AC:99:2E:01:D8:3E:13:78:60:FC:99:07:
  • 4D:2F:AB:D7:C9:02:20:70:5F:CC:4D:76:9B:17:18:F3:
  • FE:F0:1E:40:16:70:73:14:67:DA:1F:1C:8B:12:A1:D8:
  • 3D:7A:38:1E:E2:8A:AA
  • 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 : Mar 7 18:16:31.742 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C7:D6:17:48:49:E4:46:28:48:0A:05:
  • B7:24:2A:4B:B3:25:49:E1:D9:5B:0D:C9:2F:55:E5:1D:
  • F1:EE:60:2A:EE:02:21:00:89:E7:E6:4B:5C:C6:D3:BB:
  • AC:FA:76:5F:CE:75:E8:2A:67:B1:36:69:32:98:96:2E:
  • C6:48:CA:86:CC:E8:35:43