SSL check results of kogitoapp.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for kogitoapp.com 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, 14 Nov 2023 02:05:24 +0000

The mailservers of kogitoapp.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @kogitoapp.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.kogito.network
2a03:b0c0:3:e0::2ad:1001
10
supported
mail.kogito.network
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
1 s
mail.kogito.network
68.183.210.237
10
supported
mail.kogito.network
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.kogito.network

Certificate chain
  • mail.kogito.network
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mail.kogito.network
Alternative Names
  • mail.kogito.network
  • postfixadmin.kogito.network
  • spam.kogito.network
  • webmail.kogito.network
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-09-10
Not valid after
2023-12-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
80:29:D5:B1:D1:56:6F:2D:6B:44:D9:EA:B8:F9:65:92:F2:3F:E1:88:E9:71:A5:2B:D3:28:68:D9:04:C4:07:EB
SHA1
BA:13:6D:CF:0E:A8:90:CB:3F:B6:D2:11:67:25:42:3E:70:BA:02:80
X509v3 extensions
subjectKeyIdentifier
  • F2:5E:D8:5F:0C:57:28:F5:CB:14:A4:81:8C:91:49:77:D9:B0:E8:25
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Sep 10 01:30:35.929 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D9:7D:9D:C2:D9:7D:76:0B:05:37:B2:
  • 4C:E8:13:99:A0:99:D5:41:B8:13:45:01:45:B7:52:A7:
  • 9A:B4:32:82:EB:02:20:6C:8C:36:E5:B5:B6:E5:87:0A:
  • 76:45:35:E0:02:BC:40:3D:F3:F1:88:AC:9E:04:38:F3:
  • 69:57:E9:AE:1F:64:D2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
  • 03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
  • Timestamp : Sep 10 01:30:35.929 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C3:F4:6E:0F:06:C2:68:D1:ED:7D:75:
  • F4:D0:3E:1A:F9:A8:63:5A:D2:F3:44:88:E8:B6:D0:17:
  • 7B:5F:1A:5E:35:02:20:47:FA:4B:B7:25:0D:D0:34:CB:
  • DB:BB:7A:A0:76:E3:7D:F3:18:77:54:82:72:C5:7D:CC:
  • 45:D7:CF:4F:22:C2:D0