SSL-Tools

SSL check results of parsianhost.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for parsianhost.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 Sat, 27 Apr 2024 06:57:51 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.parsianhost.com
31.214.174.112
 10
supported
mail2.parsianhost.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
34 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail2.parsianhost.net

Certificate chain
  • mail2.parsianhost.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail2.parsianhost.net
Alternative Names
  • mail.parsianhost.com
  • mail.parsianhost.ir
  • mail2.parsianhost.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-12
Not valid after
2024-05-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EE:A7:88:6E:C0:E8:83:F2:C1:5A:4A:93:DC:61:D4:FF:44:1C:E8:B3:FD:0D:4C:32:96:C7:97:65:92:45:D9:F5
SHA1
EE:5E:64:79:9B:F1:F9:CD:8B:F1:49:B6:32:70:A4:CA:76:05:A2:D8
X509v3 extensions
subjectKeyIdentifier
  • 28:42:93:93:CB:A0:74:CD:88:66:56:6F:E8:BF:8A:4B:7A:31:0C:1B
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 : Feb 12 13:54:09.832 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:9C:49:BE:FF:B3:26:D5:75:57:FC:A5:
  • 47:C3:D8:E7:D0:F3:41:C4:EF:44:C3:0D:CD:6D:56:A6:
  • B1:2A:B9:B1:04:02:21:00:E7:22:F6:B9:85:20:CB:24:
  • BD:75:38:00:85:63:38:BA:CB:E0:A5:22:6F:5B:5C:9D:
  • DF:A0:0E:67:74:60:7E:F9
  • 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 12 13:54:09.909 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:22:6E:35:09:AB:CF:04:94:BB:41:7B:85:
  • 74:81:64:BF:13:FA:D2:1E:FE:E6:82:34:3A:97:CB:B1:
  • A8:3C:92:6E:02:21:00:83:DB:D3:9A:C1:47:F0:D1:83:
  • 12:4E:1A:19:A6:BC:30:20:5F:26:93:72:25:3C:C3:16:
  • D8:18:8C:B7:21:1F:C1