SSL-Tools

SSL check results of funktel.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for funktel.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, 02 Sep 2024 09:06:09 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail09.funktel.com
80.146.184.27
 10
supported
*.funktel.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s
mail10.funktel.com
80.146.184.29
 10
supported
*.funktel.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s
mforward.dtag.de
194.25.242.123
Results incomplete
50
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.funktel.com

Certificate chain
  • *.funktel.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.funktel.com
Alternative Names
  • *.funktel.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-02
Not valid after
2024-12-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
96:70:19:96:1F:07:02:C8:5E:AC:5B:B4:49:7B:4D:4B:B9:92:58:E1:1B:48:82:00:2E:06:62:A1:99:91:12:F9
SHA1
C3:E0:D8:48:BE:23:65:C5:6D:2F:32:8F:1A:3A:A6:98:88:58:A4:37
X509v3 extensions
subjectKeyIdentifier
  • 59:D3:5A:5D:A6:64:5B:48:7A:EA:A8:BF:0F:EB:3D:A9:F2:78:5E:1D
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Sep 2 08:44:38.354 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:50:CA:47:34:88:65:DA:B5:F9:1C:CC:CE:
  • 69:6A:BC:3D:04:D3:58:4E:A9:48:57:AD:75:E6:02:AE:
  • 8E:51:4E:0A:02:21:00:9C:E6:DC:51:F7:9D:55:71:14:
  • F2:F7:18:88:74:65:3A:01:C0:25:0A:56:AC:B3:DC:B4:
  • 59:8A:EF:86:33:EE:BA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Sep 2 08:44:38.567 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6A:C8:B7:36:18:34:8D:A5:BA:66:3E:48:
  • C8:F6:F5:EA:8C:71:7D:51:0E:2F:F7:A9:BE:D0:AD:48:
  • D2:71:23:76:02:20:1A:08:99:F6:50:4B:EA:DC:5C:C1:
  • D3:D8:DE:DF:21:EE:E2:77:30:EA:0F:B0:19:E7:ED:49:
  • 2C:22:0D:81:FF:CA