SSL-Tools

SSL check results of persianhawk.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for persianhawk.com 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 Wed, 24 Apr 2024 18:03:41 +0000

The mailservers of persianhawk.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @persianhawk.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.persianhawk.com
194.180.224.133
 10
supported
mail.persianhawk.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.persianhawk.com

Certificate chain
  • mail.persianhawk.com
    • 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.persianhawk.com
Alternative Names
  • imap.persianhawk.com
  • mail.persianhawk.com
  • pop.persianhawk.com
  • smtp.persianhawk.com
  • webmail.persianhawk.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-24
Not valid after
2024-07-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C2:E3:E4:91:93:7C:A8:BD:AB:40:55:A2:D4:E9:6F:C5:42:B0:28:B1:53:40:4B:E6:68:EA:2E:98:68:BB:0B:B7
SHA1
2F:84:C9:6D:15:C1:A5:F9:EC:FE:9D:42:B8:E6:27:E3:8C:41:C5:E6
X509v3 extensions
subjectKeyIdentifier
  • C1:3C:1D:4E:58:A1:F1:F5:05:18:59:11:93:D6:5F:1E:43:45:B6:EA
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Apr 24 05:03:46.264 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FB:22:1E:A6:C9:47:45:AC:67:CB:A8:
  • 50:48:99:DC:45:E4:0A:5E:BF:49:4D:16:10:A5:B5:4B:
  • E2:79:2C:14:3A:02:21:00:E1:15:BC:53:20:7A:04:61:
  • B1:68:BA:C2:82:4A:66:6D:0B:73:C9:48:2B:EC:C9:A9:
  • 19:99:55:AD:4E:66:59:23
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Apr 24 05:03:46.260 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:01:21:C6:0E:9D:89:C7:E2:06:24:C4:97:
  • E4:B9:DF:68:2E:69:11:78:5D:1E:4E:AD:54:61:C5:F6:
  • 15:88:52:58:02:20:1E:3E:8F:F1:22:6F:7B:5B:90:06:
  • DD:0A:10:27:5D:9D:3D:80:06:10:EF:DE:D4:13:3A:9F:
  • 91:B9:E9:D9:C4:8E