SSL-Tools

SSL check results of vanboekel-gmbh.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for vanboekel-gmbh.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 Fri, 21 Feb 2025 14:03:13 +0000

The mailservers of vanboekel-gmbh.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @vanboekel-gmbh.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx00.udag.de
62.146.106.39
 10
supported
mx00.udag.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
mx01.udag.de
62.146.106.40
 20
supported
mx00.udag.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 @vanboekel-gmbh.com address so far. Test mail delivery

Certificates

First seen at:

CN=mx00.udag.de

Certificate chain
  • mx00.udag.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx00.udag.de
Alternative Names
  • mx00.udag.de
  • mx01.udag.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-01-28
Not valid after
2025-04-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E8:E7:F5:FB:D8:71:07:FA:4F:3D:65:A7:F3:77:B8:AB:F8:9A:92:B1:1F:91:BB:70:2B:93:75:C0:45:EA:2F:98
SHA1
EF:DF:F6:2A:16:3E:EB:73:DB:3F:90:C9:12:C6:43:A3:BF:F4:08:30
X509v3 extensions
subjectKeyIdentifier
  • 00:25:7B:42:4A:1E:F3:0B:32:3B:12:69:78:88:9D:FD:27:6F:7F:0D
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 : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Jan 28 23:02:19.584 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1D:55:0A:94:F2:4B:33:62:AE:1E:55:00:
  • 96:78:22:E2:E7:9F:89:23:0A:29:D3:8C:4C:EE:B0:3B:
  • EF:BC:9A:E5:02:20:2B:3E:4D:90:CE:B4:E3:05:7A:35:
  • C2:F5:DC:5D:5C:1D:DE:30:3F:83:6A:DB:8F:1C:C9:8C:
  • 22:7B:7C:FB:28:6E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 28 23:02:19.611 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E2:07:39:06:A4:59:86:88:94:4E:77:
  • 28:E9:65:C5:17:A3:65:C0:DD:72:8C:3B:CB:A3:A5:A9:
  • C7:1F:CF:ED:37:02:21:00:E1:D1:1B:DB:02:43:7C:0F:
  • CA:AA:FD:FC:4D:AC:07:ED:E2:EA:8E:C8:60:12:E7:FE:
  • 0F:B9:B5:D9:6D:71:78:47