SSL check results of cogindo.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for cogindo.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 Sat, 18 Oct 2025 07:14:05 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
owl.servers.cogindo.tech
2a01:4f8:c012:e1d9::1
50
supported
mail.cogindo.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s
owl.servers.cogindo.tech
167.235.243.196
50
supported
mail.cogindo.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.cogindo.net

Certificate chain
  • mail.cogindo.net
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E7
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mail.cogindo.net
Alternative Names
  • imap.cogindo.net
  • mail.cogindo.net
  • owl.servers.cogindo-tech.com
  • owl.servers.cogindo.tech
  • pop3.cogindo.net
  • smtp.cogindo.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E7
validity period
Not valid before
2025-10-17
Not valid after
2026-01-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D5:D5:D5:F0:2C:3A:AA:17:2A:3A:EC:7D:51:60:00:9E:BB:D3:14:D6:1B:90:F5:1A:A8:1E:76:48:B3:6B:F0:AF
SHA1
63:0C:92:C1:F5:19:80:B9:95:12:E5:04:9C:98:E5:AB:E2:89:89:E9
X509v3 extensions
subjectKeyIdentifier
  • 9A:27:47:D5:34:95:42:46:4A:7C:07:5F:AC:DA:FB:30:8C:5A:9E:26
authorityKeyIdentifier
  • keyid:AE:48:9E:DC:87:1D:44:A0:6F:DA:A2:E5:60:74:04:78:C2:9C:00:80
authorityInfoAccess
  • CA Issuers - URI:http://e7.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e7.c.lencr.org/89.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 49:9C:9B:69:DE:1D:7C:EC:FC:36:DE:CD:87:64:A6:B8:
  • 5B:AF:0A:87:80:19:D1:55:52:FB:E9:EB:29:DD:F8:C3
  • Timestamp : Oct 17 22:13:29.491 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4A:65:55:33:CD:24:B0:78:8B:E4:85:E2:
  • F0:64:8B:90:BA:52:D6:9B:F7:73:0D:04:E3:7A:2E:9F:
  • 32:12:E1:48:02:21:00:D7:0E:BF:99:6E:E1:41:04:B3:
  • C7:18:A2:2E:83:B8:AB:82:E4:7D:C6:7A:DA:CC:A5:23:
  • 1A:9A:D9:E4:14:43:FA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:86:D4:C7:28:AA:6F:FE:BA:03:6F:78:2A:4D:01:91:
  • AA:CE:2D:72:31:0F:AE:CE:5D:70:41:2D:25:4C:C7:D4
  • Timestamp : Oct 17 22:13:29.494 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A3:5F:11:DF:7F:2B:B7:B3:40:59:D2:
  • ED:5C:36:3B:F3:6E:23:8E:9F:EC:DD:9B:F3:A7:B9:C0:
  • 73:77:8D:C2:F1:02:21:00:FF:20:FE:AD:C0:CA:12:BB:
  • 88:73:56:67:32:8F:CD:AD:67:08:4C:DF:B8:CF:E4:0F:
  • 46:AE:30:08:6F:4E:CE:86