SSL-Tools

SSL check results of tecvise.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for tecvise.de 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, 02 Jun 2023 06:54:19 +0000

The mailservers of tecvise.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @tecvise.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
tecvise-de.mail.cloud.nospamproxy.com
193.37.132.131
 0
supported
*.mail.cloud.nospamproxy.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
tecvise-de.mail.cloud.nospamproxy.com
193.37.132.171
 0
supported
*.mail.cloud.nospamproxy.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.mail.cloud.nospamproxy.com

Certificate chain
  • *.mail.cloud.nospamproxy.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.cloud.nospamproxy.com
Alternative Names
  • *.mail.cloud.nospamproxy.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-03-18
Not valid after
2023-06-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
19:8C:F0:AF:3D:4A:4D:1B:20:64:38:5A:D5:C5:C2:2C:19:EB:2B:82:F2:BD:15:E4:0B:12:39:35:7F:4A:B4:6A
SHA1
85:85:11:E1:C0:25:9D:48:4B:B1:4A:0E:CE:ED:29:FE:F5:B4:87:DA
X509v3 extensions
subjectKeyIdentifier
  • 46:48:36:2C:84:A2:A3:3F:03:B4:63:74:5B:8F:9D:14:D3:07:D5:08
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Mar 18 07:19:28.456 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6A:41:3B:17:67:CB:C1:B5:47:CC:48:47:
  • 54:1B:D7:71:46:8A:87:52:37:8B:A6:83:4B:C2:E5:72:
  • A2:ED:E5:6F:02:20:68:F3:E4:DB:55:89:74:83:3A:1D:
  • B1:47:A6:F5:96:0D:BD:C0:F0:98:9C:28:19:01:32:68:
  • 2C:F8:39:92:DC:2C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Mar 18 07:19:28.491 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:BF:76:24:A5:87:3F:F2:F7:AB:8E:DA:
  • 1F:0F:3E:AE:55:3A:2D:72:98:D2:9D:19:7F:D0:9F:F0:
  • 9A:B8:9F:CA:D4:02:21:00:94:BD:3E:D1:6C:90:F7:E0:
  • 5F:89:C2:D6:2D:4E:5E:D1:D8:80:B1:52:E0:1A:F5:83:
  • 4A:E0:6E:7A:C3:0B:EE:37