SSL-Tools

SSL check results of customer-relay1.web-server.biz

NEW You can also bulk check multiple servers.

Discover if the mail servers for customer-relay1.web-server.biz 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, 11 Dec 2023 14:37:34 +0000

The mailservers of customer-relay1.web-server.biz can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @customer-relay1.web-server.biz addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
customer-relay1.web-server.biz
185.181.105.9
 10
supported
customer-relay1.web-server.biz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @customer-relay1.web-server.biz address so far. Test mail delivery

Certificates

First seen at:

CN=customer-relay1.web-server.biz

Certificate chain
  • customer-relay1.web-server.biz
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • customer-relay1.web-server.biz
Alternative Names
  • customer-relay1.web-server.biz
  • smtp-relay1.web-server.biz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-10-23
Not valid after
2024-01-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
55:F4:14:10:35:DF:E9:81:2F:48:3F:A9:05:7A:9E:BA:52:8F:5B:71:79:16:4A:8F:99:B9:28:62:54:28:7C:18
SHA1
3F:D7:E8:27:1A:6A:41:9A:9F:EC:32:B0:23:80:0A:FA:E7:C0:32:70
X509v3 extensions
subjectKeyIdentifier
  • 2B:BF:86:7F:5F:BD:6F:99:29:7B:BD:AB:A2:C5:C9:8A:13:56:F4:1C
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 : Oct 23 13:10:04.774 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:77:84:72:6E:FA:55:B4:59:4F:2A:8B:80:
  • 43:1F:DE:C6:D6:7E:C9:8F:D9:00:B7:40:E0:4B:42:12:
  • 08:B4:A8:9E:02:21:00:DB:EA:88:2C:41:01:A5:E9:51:
  • 90:D1:64:08:5D:EB:7D:D4:C2:B3:7C:94:18:A2:32:77:
  • 0D:35:EC:C0:31:F3:EB
  • 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 : Oct 23 13:10:04.769 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F4:B4:FE:37:02:2A:69:7F:8B:BC:0E:
  • C1:06:76:DD:48:A1:3D:43:88:BA:6E:37:F1:10:56:FA:
  • 02:8E:53:EF:15:02:21:00:95:A7:65:FB:BC:6F:C8:81:
  • 65:3F:21:EA:AB:5F:D0:56:49:07:A5:A0:1B:61:C1:87:
  • 18:24:1C:D8:AC:4E:4E:B4