SSL check results of boettcher.at

NEW You can also bulk check multiple servers.

Discover if the mail servers for boettcher.at 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

Report created Tue, 10 May 2022 09:02:01 +0000

We can not guarantee a secure connection to the mailservers of boettcher.at!

Please contact the operator of boettcher.at and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/boettcher.at

Servers

Incoming Mails

These servers are responsible for incoming mails to @boettcher.at addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.boettcher.de
195.14.245.6
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mailrelay.netcologne.de
194.8.194.96
20
supported
mailrelay.netcologne.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mailrelay.netcologne.de

Certificate chain
  • mailrelay.netcologne.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mailrelay.netcologne.de
Alternative Names
  • mailrelay.netcologne.de
  • mailrelay3.netcologne.de
  • mailrelay4.netcologne.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-05-03
Not valid after
2022-08-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
10:17:8D:9E:2F:93:74:12:5D:85:4B:36:63:BA:CA:25:22:CA:12:45:57:73:3D:7C:E0:09:8D:69:76:DE:AB:8A
SHA1
D6:70:87:DE:D5:B6:3D:D9:12:34:40:9C:57:48:76:1C:53:7E:6D:F6
X509v3 extensions
subjectKeyIdentifier
  • B4:B7:5F:50:00:AF:7E:0F:46:21:14:B1:C9:C0:EF:F4:36:E0:2A:EF
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 : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : May 3 07:07:28.652 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7D:AC:2D:91:6F:3E:D3:76:89:64:65:30:
  • CA:6C:EC:E1:F0:73:94:E6:F0:B1:C0:38:F4:5C:2B:D7:
  • E5:37:1E:F0:02:21:00:F6:E0:4F:71:47:AB:1C:4C:AC:
  • A7:18:46:74:C7:5D:46:10:C0:BB:D5:9B:98:51:04:4B:
  • DD:CB:1A:6A:DF:08:00
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : May 3 07:07:29.078 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:82:9D:5F:CA:97:C3:03:43:74:C7:2C:
  • 59:BD:80:6E:68:5E:7D:81:FF:A7:CB:C1:17:06:DF:37:
  • 58:A4:E2:49:ED:02:20:1A:E4:DC:66:ED:1D:0A:29:86:
  • E8:EB:02:F7:34:80:2A:91:4F:15:2B:6C:92:37:74:58:
  • 0D:3C:5E:20:B3:01:D0