SSL-Tools

SSL check results of vogelbusch-biopharma.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for vogelbusch-biopharma.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 Tue, 15 Jun 2021 05:56:24 +0000

The mailservers of vogelbusch-biopharma.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @vogelbusch-biopharma.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail4.vogelbusch.com
80.245.197.240
 10
supported
mail4.vogelbusch.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail2.vogelbusch.com
80.245.195.203
Results incomplete
100 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail4.vogelbusch.com

Certificate chain
  • mail4.vogelbusch.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • mail4.vogelbusch.com
Alternative Names
  • mail4.vogelbusch.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-19
Not valid after
2021-07-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
96:A5:8D:44:69:07:ED:11:0D:C7:07:91:78:CB:5B:AD:50:AF:01:54:25:CF:0A:5E:76:56:07:E1:E7:09:8E:F2
SHA1
13:CD:F4:0A:D0:AB:3A:A9:C5:AA:31:A5:61:1B:70:1C:85:FD:73:0A
X509v3 extensions
subjectKeyIdentifier
  • BE:81:B1:ED:0A:D3:E4:C4:30:49:D6:80:80:6D:6D:40:4F:BF:4D:24
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Apr 19 10:40:21.788 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E3:79:17:DA:E1:A8:A4:C2:3A:8D:D0:
  • 56:4F:32:78:4A:D3:46:D0:A0:19:01:B7:AF:81:39:05:
  • 5F:02:C0:2F:A7:02:20:65:30:07:D5:F6:80:7B:8A:93:
  • A5:14:5F:04:A1:D6:FE:93:3F:38:B7:05:BC:83:BE:FE:
  • D2:3B:DA:19:97:D2:63
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Apr 19 10:40:21.807 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:22:02:42:B4:05:2B:1D:92:D6:67:EE:84:
  • F4:45:74:C7:29:0F:14:F3:D3:43:8E:05:E9:09:78:26:
  • 83:18:78:94:02:21:00:9A:3E:CC:03:F4:14:1C:02:5A:
  • 9B:EF:66:2B:4A:EA:21:0B:39:BA:F5:62:14:3F:EF:E4:
  • C9:51:ED:3A:F5:B0:68