SSL check results of antwort.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for antwort.net 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, 06 Apr 2021 09:04:24 +0000

The mailservers of antwort.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @antwort.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.antwort.net
2001:41d0:8:b415::1
10
supported
mx.antwort.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s
mx.antwort.net
5.39.95.21
10
supported
mx.antwort.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
13 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx.antwort.net

Certificate chain
  • mx.antwort.net
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • mx.antwort.net
Alternative Names
  • mx.antwort.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-05
Not valid after
2021-07-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
52:F2:5C:8A:F4:A1:34:A9:45:74:CE:EC:C8:A8:CF:06:6F:F0:59:FF:C4:3A:B2:DE:86:D7:E9:4C:08:E6:2E:A5
SHA1
08:DF:CF:A9:03:F7:8C:6D:68:26:23:ED:78:BD:27:46:27:A2:A3:E0
X509v3 extensions
subjectKeyIdentifier
  • B8:E7:B0:A0:80:7C:4B:E1:F7:1E:0B:BA:44:FE:6C:A2:7F:F5:D6:96
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 : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Apr 5 23:08:31.503 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8C:CD:46:53:60:66:51:11:76:16:A5:
  • 62:FD:F5:76:43:7E:29:24:0A:24:15:D6:F3:8A:9B:3F:
  • D9:1D:6C:A6:C2:02:21:00:F7:A1:1D:1E:5C:27:D3:5C:
  • 05:3F:B7:AF:AE:B4:FD:3E:62:8E:FD:9D:56:C5:75:3D:
  • BC:24:5D:D8:04:51:44:3F
  • 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 : Apr 5 23:08:31.654 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:79:5F:06:47:50:5E:6F:B5:69:A5:8D:79:
  • A2:D5:E3:78:E3:0F:41:58:57:29:05:66:52:DA:39:40:
  • 1A:DA:54:8D:02:21:00:89:60:03:6B:11:F1:B8:DA:37:
  • 1F:9C:B0:6C:4C:4E:63:4E:4D:DF:5F:A7:6D:24:B9:6D:
  • 56:C7:2C:77:44:E4:DA