SSL-Tools

SSL check results of openetworks.pl

NEW You can also bulk check multiple servers.

Discover if the mail servers for openetworks.pl 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 Tue, 23 Apr 2024 08:25:08 +0000

The mailservers of openetworks.pl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @openetworks.pl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx0.openetworks.pl
51.83.214.76
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.openetworks.pl
51.83.138.250
 20
supported
mail.openetworks.pl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mx0.openetworks.pl
51.83.214.76
Results incomplete
100 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.openetworks.pl

Certificate chain
  • mail.openetworks.pl
    • 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.openetworks.pl
Alternative Names
  • mail.openetworks.pl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-02
Not valid after
2024-05-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A1:57:9F:E7:C9:02:5E:72:F8:46:EF:1C:57:F1:0E:75:73:4B:6F:5B:4E:CD:36:97:4D:FA:38:49:49:C1:D5:3D
SHA1
2E:5D:EE:7D:99:36:B0:4D:11:D3:99:E9:F4:3E:43:2A:C8:1B:27:4D
X509v3 extensions
subjectKeyIdentifier
  • 96:7D:28:B4:38:B0:45:9E:D6:7C:2D:8D:07:02:EA:E9:6D:DC:E7:F6
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 2 11:00:28.022 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4C:E9:01:50:F8:99:07:5E:F4:F2:0A:98:
  • B8:2F:B4:55:C5:78:C9:62:65:2F:F0:07:57:53:30:FD:
  • E9:3B:01:98:02:21:00:C4:57:5C:92:A3:5B:0C:74:27:
  • 4D:50:6F:0D:11:24:21:F8:86:BC:29:1A:F1:C1:5B:C9:
  • 5E:C8:E3:8A:30:75:BF
  • 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 2 11:00:28.031 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C8:4C:FD:24:C5:84:54:BF:D4:E4:E1:
  • 6E:F5:B7:81:EC:0C:DC:93:EA:51:2A:8D:A5:52:E1:07:
  • AC:CB:CD:B2:23:02:20:62:62:7F:F0:DE:18:58:2A:78:
  • 5C:D0:3F:47:B1:14:AE:FF:C2:EB:49:86:6E:5E:5F:9B:
  • CC:91:7A:4E:F3:05:33