SSL-Tools

SSL check results of fue-europe.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for fue-europe.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 Sat, 27 Jul 2024 00:30:50 +0000

The mailservers of fue-europe.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @fue-europe.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.skinpro.de
2a01:4f8:200:52b4::2
 0
supported
skinpro.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mail.skinpro.de
144.76.174.181
 0
supported
skinpro.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 @fue-europe.com address so far. Test mail delivery

Certificates

First seen at:

CN=skinpro.de

Certificate chain
  • skinpro.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)
  • skinpro.de
Alternative Names
  • mail.skinpro.de
  • skinpro.de
  • www.skinpro.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-07-04
Not valid after
2024-10-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
17:60:72:39:44:3A:FD:42:3C:3B:3F:30:E6:24:88:2C:25:8D:EF:44:59:B7:1E:74:AB:1D:38:D6:F7:98:0D:71
SHA1
FB:B7:BA:C5:47:19:4C:99:47:E6:BA:87:E6:AC:61:25:64:DE:E3:7D
X509v3 extensions
subjectKeyIdentifier
  • BB:B7:2A:A4:E8:B5:D4:03:A9:D7:78:8E:57:30:93:F0:EB:8F:AD:42
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Jul 4 01:07:27.289 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A1:03:F1:73:65:EF:25:D4:23:3A:91:
  • 63:D8:BA:BE:B4:EC:EF:9B:4A:22:2E:18:23:17:3F:77:
  • F3:E7:6C:16:10:02:20:04:1E:F0:43:22:1B:F8:4E:DE:
  • 79:4C:69:59:C2:6C:A8:09:5B:C6:3B:ED:60:29:89:2E:
  • B4:42:B2:8F:4D:51:75
  • 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 : Jul 4 01:07:27.491 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F2:54:8C:BB:64:55:93:88:AA:CE:AE:
  • D0:2B:B7:D5:C1:2F:E4:F1:F9:2A:AB:10:DD:FE:44:3E:
  • 15:D0:D9:4A:7B:02:20:29:CE:80:A8:3E:CC:39:37:19:
  • CD:0E:F3:E8:90:72:D0:AE:27:3D:1D:0C:47:37:3D:3E:
  • 51:D8:45:C9:4E:22:3E