SSL check results of afwasser.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for afwasser.nl 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:33:14 +0000

We can not guarantee a secure connection to the mailservers of afwasser.nl!

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

/mailservers/afwasser.nl

Servers

Incoming Mails

These servers are responsible for incoming mails to @afwasser.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
afwasser.nl
2a02:c207:2046:6105::1
10
supported
afwasser.nl
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
47 s
afwasser.nl
161.97.124.213
Results incomplete
10
unsupported
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 @afwasser.nl address so far. Test mail delivery

Certificates

First seen at:

CN=afwasser.nl

Certificate chain
  • afwasser.nl
    • remaining
    • 384 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • afwasser.nl
Alternative Names
  • afwasser.nl
  • mail.afwasser.nl
  • www.afwasser.nl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-01-20
Not valid after
2022-04-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AF:8B:7E:E1:77:16:50:47:E2:26:2A:7F:01:7A:21:F4:7A:6C:54:67:8B:AF:25:B3:4A:9E:0A:1C:B0:49:13:53
SHA1
89:F1:E6:A7:01:64:5E:B4:D3:61:7B:B1:F1:2C:40:C7:19:73:F0:E7
X509v3 extensions
subjectKeyIdentifier
  • B6:39:F5:97:D4:5C:E4:F4:69:1E:3A:DF:4A:B6:8D:2A:CD:3A:4C:D4
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 : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
  • EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
  • Timestamp : Jan 20 21:53:00.492 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:42:A2:63:9A:FF:B5:C4:A9:68:4D:CF:D1:
  • 25:4C:49:FD:0E:81:87:FC:92:C3:A1:6F:A0:94:7A:9C:
  • 88:78:42:06:02:21:00:AF:20:98:C1:D3:26:48:72:16:
  • C0:C2:41:1C:F0:7A:04:C6:95:C0:B3:CA:3A:12:03:B2:
  • 65:6A:79:70:D6:FA:FD
  • 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 : Jan 20 21:53:00.531 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:09:05:93:64:FB:96:8D:5E:BF:DE:AC:F5:
  • A3:2A:8F:86:0C:79:D0:6F:87:69:FF:09:9C:1C:7D:9C:
  • 10:CF:05:A9:02:20:4C:0B:00:0A:93:0A:D3:D8:E3:E8:
  • FC:AD:E0:9D:77:62:8D:A1:9F:D7:9C:D5:D2:39:AD:3E:
  • 1C:DA:8D:0D:81:2B