SSL-Tools

SSL check results of mail.webcam-team.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.webcam-team.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 Tue, 15 Jul 2025 15:18:15 +0000

The mailservers of mail.webcam-team.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.webcam-team.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.webcam-team.de
136.243.79.242
 -
supported
mail.webcam-team.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.webcam-team.de
2a01:4f8:212:2dcc::2
 -
supported
mail.webcam-team.de
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 @mail.webcam-team.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.webcam-team.de

Certificate chain
  • mail.webcam-team.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.webcam-team.de
Alternative Names
  • mail.webcam-team.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-07-13
Not valid after
2025-10-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
08:62:8B:F4:5A:B6:8D:2E:BF:FF:2A:01:8D:62:DC:79:EA:1D:F6:43:05:D3:CE:4C:6E:98:4C:1E:48:1A:B8:B6
SHA1
2F:02:A9:B1:9C:42:04:B6:C4:7D:82:36:66:23:07:2E:EF:7F:08:68
X509v3 extensions
subjectKeyIdentifier
  • A5:CE:D4:44:B2:29:CA:24:45:DC:95:BA:46:5F:F5:0F:D5:B3:3A:5F
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/57.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Jul 13 11:44:39.473 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:21:00:FB:ED:36:A4:AE:08:92:EF:C8:2D:A4:
  • 26:17:7C:CB:85:31:12:13:22:2C:5F:A4:C6:07:1A:86:
  • 1F:FC:7A:65:B5:02:1F:25:15:63:63:B0:02:CD:AE:05:
  • 06:9D:95:38:2F:84:29:30:7C:59:92:E5:DF:70:91:76:
  • 4A:B4:3B:69:21:EB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jul 13 11:44:39.473 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F9:53:3B:F7:5B:C4:57:DD:F1:AC:70:
  • BB:32:9A:B1:50:86:54:CC:F4:31:75:3C:F9:A0:C3:91:
  • 69:2E:FB:2D:DE:02:21:00:AE:BD:7B:DA:BD:5A:D1:77:
  • DC:E9:47:85:5C:78:F9:83:BA:92:C3:74:6E:37:74:5D:
  • 4B:20:3A:86:2D:77:4B:91