SSL-Tools

SSL check results of festivalmariano.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for festivalmariano.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 Fri, 08 Dec 2023 14:49:54 +0000

We can not guarantee a secure connection to the mailservers of festivalmariano.com!

Please contact the operator of festivalmariano.com and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/festivalmariano.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
jrcomm01.jrcompusolutions.com
208.87.134.179
 10
supported
jrcomm01.p2cphone.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • SSLv3
6 s
mail.festivalmariano.com
208.87.134.179
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=jrcomm01.p2cphone.com

Certificate chain
  • jrcomm01.p2cphone.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • jrcomm01.p2cphone.com
Alternative Names
  • jrcomm01.p2cphone.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-11-13
Not valid after
2024-02-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AC:3A:6D:81:AC:0E:02:3B:AD:92:A1:FD:FF:CE:22:05:76:B5:BD:EF:D4:62:FA:6B:F2:51:CE:94:11:47:46:FB
SHA1
1B:A7:C9:6C:94:CE:E0:B2:EA:EE:96:76:7C:F9:31:9A:DB:D1:82:0D
X509v3 extensions
subjectKeyIdentifier
  • 90:0F:CB:F2:9D:63:1D:21:C3:80:BD:76:1A:7F:68:2B:37:0B:C2:5C
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 : Nov 13 05:37:10.228 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:34:55:42:94:CB:D2:3F:21:22:C2:C1:A3:
  • 22:F6:28:C7:3D:6C:63:3B:33:DA:82:21:95:16:FF:CB:
  • 94:C8:81:BF:02:21:00:B3:1B:0F:CD:89:C1:71:6B:4C:
  • 93:3A:0E:F6:7B:9F:0B:58:81:8D:FB:F7:04:0B:03:C7:
  • 81:04:7B:C1:56:EB:2C
  • 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 : Nov 13 05:37:10.248 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:24:CF:58:EE:3E:6F:60:55:73:FA:45:FF:
  • 7E:D0:D2:9E:E0:1F:DD:D9:BB:4A:0E:36:BF:02:BA:28:
  • 54:FA:ED:B9:02:20:20:74:FA:E2:C4:C9:88:67:24:ED:
  • 66:7F:34:4A:80:D9:87:3E:F2:8B:B6:06:AE:DC:78:6C:
  • 54:9A:F9:93:91:6C