SSL check results of afwassers.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for afwassers.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 Thu, 20 Jan 2022 23:35:09 +0000

We can not guarantee a secure connection to the mailservers of afwassers.net!

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

/mailservers/afwassers.net

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
afwassers.net
2a02:c207:2046:6105::1
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
afwassers.net
149.210.130.129
10
supported
srv1.active8hosting.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=srv1.active8hosting.net

Certificate chain
  • srv1.active8hosting.net
    • remaining
    • 384 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • srv1.active8hosting.net
Alternative Names
  • srv1.active8hosting.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-12-05
Not valid after
2022-03-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F5:90:6B:5D:CC:5D:1E:1D:BC:86:F0:A9:C6:F4:BF:70:5C:9F:A2:44:6F:32:EC:2D:E1:AE:C1:0E:CF:B1:D3:FF
SHA1
04:EC:24:92:AF:A2:B9:F9:A4:DD:A4:C2:13:82:B7:0A:C4:44:0B:42
X509v3 extensions
subjectKeyIdentifier
  • 98:7A:14:3B:3E:0D:D3:AF:B7:78:74:D9:28:FA:6E:77:77:2E:2B:03
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 : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
  • 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
  • Timestamp : Dec 5 10:37:58.191 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5F:EB:20:6A:85:70:E8:7A:84:76:19:93:
  • C5:3A:53:4D:87:46:3C:EE:56:E5:00:90:C9:76:B8:F5:
  • 82:A6:08:D4:02:20:07:7E:82:60:E9:57:04:43:BC:1D:
  • 9B:04:68:B1:F1:EB:D7:0F:7D:1C:68:19:97:43:C8:40:
  • C5:E6:FD:7D:AD:28
  • 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 : Dec 5 10:37:58.496 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:86:40:C3:03:1E:ED:3B:03:0A:BE:CD:
  • E5:AA:60:44:6A:F6:A1:67:32:5D:58:EA:80:AF:77:B9:
  • B7:B7:43:F2:91:02:21:00:EA:B4:2F:1E:50:F5:AF:7C:
  • 19:A6:E2:8F:91:06:FF:D4:1D:6C:18:BE:A6:9F:F7:06:
  • F8:7A:A2:49:D7:02:17:02