SSL-Tools

SSL check results of royalpardazco.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for royalpardazco.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 Mon, 16 Sep 2024 13:04:07 +0000

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

Servers

Incoming Mails

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

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

Outgoing Mails

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

Certificates

First seen at:

CN=mail.royalpardazco.com

Certificate chain
  • mail.royalpardazco.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.royalpardazco.com
Alternative Names
  • mail.royalpardazco.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-07-19
Not valid after
2024-10-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
62:49:CF:DD:66:DF:C8:90:BC:D3:EE:BF:51:12:DB:58:FC:AF:EA:84:20:B3:A8:28:45:A4:DB:35:5B:EF:D8:D1
SHA1
0C:9B:3C:FA:99:08:9E:8D:E3:22:4B:1C:62:79:B7:4B:C2:71:31:87
X509v3 extensions
subjectKeyIdentifier
  • 10:EB:FA:9E:2B:2D:40:DF:E7:D0:59:21:80:8C:13:6A:0B:67:24:2A
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 : Jul 19 08:13:07.897 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3B:DC:98:F9:8A:59:F2:71:81:25:88:4B:
  • BC:04:82:32:6A:40:35:65:6B:79:B7:ED:03:8B:EA:42:
  • 81:FB:46:58:02:21:00:C6:20:80:AE:9F:0A:9A:FD:12:
  • F1:DB:84:50:27:62:0D:6B:6A:1C:AD:53:1A:C0:E7:2C:
  • F3:8F:48:8F:EC:BB:69
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Jul 19 08:13:07.897 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9C:7A:AC:E7:28:99:65:BB:85:CB:26:
  • 09:17:3B:8E:F6:0C:B6:84:F9:32:67:1E:BC:F6:E3:EB:
  • F6:EE:64:FC:63:02:20:05:2D:A1:B1:BA:98:E1:96:FA:
  • 13:A9:E1:2E:F0:89:44:A9:8E:CA:BE:D1:CA:2D:20:4B:
  • 1B:0F:9A:57:69:C0:46