SSL-Tools

SSL check results of unreal.pl

NEW You can also bulk check multiple servers.

Discover if the mail servers for unreal.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 Sat, 27 Apr 2024 05:17:11 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.unreal.pl
2a02:c207:2022:6564::1
 10
supported
mail.unreal.pl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mx.unreal.pl
207.180.197.215
 10
supported
mail.unreal.pl
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 @unreal.pl address so far. Test mail delivery

Certificates

First seen at:

CN=mail.unreal.pl

Certificate chain
  • mail.unreal.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.unreal.pl
Alternative Names
  • fio.com.pl
  • mail.kersek.pl
  • mail.rudnow.pl
  • mail.solucje.pl
  • mail.unreal.pl
  • mx.unreal.pl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-09
Not valid after
2024-05-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2D:04:AB:68:22:9F:4C:D6:0B:EA:F8:62:AE:EB:EF:32:58:C0:3B:BB:64:01:02:09:5D:ED:FB:48:CC:45:E6:C7
SHA1
74:B1:F1:A1:76:4C:BD:DC:48:DD:58:0B:77:D2:7A:67:19:26:3E:D8
X509v3 extensions
subjectKeyIdentifier
  • 18:B7:78:04:A8:E5:99:ED:72:BA:91:46:56:1E:55:2F:5C:FD:82:B9
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 : Feb 9 14:24:26.609 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8D:58:75:47:09:93:78:C0:45:00:F1:
  • 2A:84:71:F9:D4:6E:A1:F0:AC:01:35:96:74:05:B1:53:
  • 48:8E:D9:7D:7D:02:20:08:91:9A:E6:86:FB:A9:2A:F6:
  • A3:72:E6:C5:79:C8:55:84:F3:D7:E6:54:66:DA:18:A1:
  • E8:5C:2F:1A:B8:17:72
  • 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 : Feb 9 14:24:26.610 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FB:4B:18:0D:F1:3B:FA:46:82:C3:74:
  • 8C:6F:3B:5F:DB:22:6C:62:51:D3:6B:C2:79:CC:9A:60:
  • 60:AE:CC:48:A4:02:20:24:A8:A3:22:DB:4D:A0:72:C8:
  • DD:ED:02:5F:F2:60:A3:E4:47:AA:A7:D9:49:F8:4F:F1:
  • 99:81:CD:6F:55:D2:1B