SSL check results of cotown.io

NEW You can also bulk check multiple servers.

Discover if the mail servers for cotown.io 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 Wed, 14 Apr 2021 08:40:38 +0000

The mailservers of cotown.io can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @cotown.io addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.cotown.io
167.71.13.114
5
supported
mail.cotown.io
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.cotown.io

Certificate chain
  • mail.cotown.io
    • 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)
  • mail.cotown.io
Alternative Names
  • mail.cotown.io
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-11
Not valid after
2021-07-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
42:5B:F4:51:60:CE:7B:D6:52:71:78:C1:30:93:C5:4F:E7:D9:6F:08:7A:51:2C:13:42:48:D6:80:AA:FF:55:91
SHA1
F3:08:8D:C6:42:78:59:B4:6E:4C:B9:B0:C2:62:21:7F:FD:61:AF:C2
X509v3 extensions
subjectKeyIdentifier
  • 56:6C:E2:6D:56:BC:81:EC:D6:21:92:C8:60:74:C4:54:19:4B:FE:E4
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Apr 11 01:53:08.338 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F9:12:20:DB:5C:5A:58:C7:70:3F:66:
  • A8:EF:CF:7D:A9:A5:AF:AB:49:1D:E6:F2:8A:3B:AA:C0:
  • A5:0D:9A:2F:03:02:21:00:C0:3E:C2:21:5F:71:2F:E5:
  • 26:B2:60:5C:59:75:8B:B5:EF:96:F4:31:05:49:28:A3:
  • 6F:B5:CE:07:C9:BB:B4:F6
  • 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 11 01:53:08.339 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:27:2C:73:F4:29:E0:98:C6:DD:22:21:F0:
  • B1:F0:A2:1C:CF:73:87:EB:E8:52:0C:4E:8B:73:6B:40:
  • 92:7F:D6:60:02:21:00:BC:FD:BD:B2:67:11:11:B2:6D:
  • F4:40:A6:00:C7:CD:4F:8B:37:8B:E2:E8:36:C2:A2:2C:
  • A4:32:39:D5:0C:58:39