SSL-Tools

SSL check results of heider.in

NEW You can also bulk check multiple servers.

Discover if the mail servers for heider.in 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

JSON Refresh

Report created Fri, 10 May 2024 18:50:42 +0000

We can not guarantee a secure connection to the mailservers of heider.in!

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

/mailservers/heider.in

Servers

Incoming Mails

These servers are responsible for incoming mails to @heider.in addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.heider.in
93.230.192.75
 0
supported
mail.heider.in
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s
smtp-pulse.com
3.75.113.112
Results incomplete
15
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.heider.in

Certificate chain
  • mail.heider.in
    • 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.heider.in
Alternative Names
  • mail.heider.in
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-17
Not valid after
2024-07-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
78:27:87:0C:3A:7A:F1:9B:3B:3E:1F:9A:A5:3C:54:3F:18:A8:79:A6:0C:B8:52:D6:89:65:70:F8:F9:81:D9:58
SHA1
B6:CC:04:3A:5E:96:93:06:10:D5:42:0C:F3:9F:21:54:13:35:13:3C
X509v3 extensions
subjectKeyIdentifier
  • 22:9B:7E:A7:E7:B9:57:F2:D3:D4:DB:68:2F:76:C3:63:57:11:3F: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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 17 02:44:14.892 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:46:CD:23:88:59:6C:D8:C3:78:57:EF:F1:
  • 78:C1:E3:51:C6:7E:C0:3B:38:EE:1D:84:4D:A0:2F:69:
  • 52:A2:AF:39:02:20:08:45:64:EB:73:4F:F6:29:7F:1B:
  • B9:C0:1B:C4:98:32:89:E5:CF:8F:D7:86:E9:4A:67:A3:
  • C0:57:99:50:59:EA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 17 02:44:14.889 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B3:85:A3:7B:7E:2E:EA:8E:E9:1F:59:
  • 20:B2:E5:11:88:26:5C:D5:07:78:CC:D5:8D:D9:66:2D:
  • 3D:4C:B4:A7:3D:02:20:0B:17:73:E8:B8:E4:EF:E0:D9:
  • 20:09:43:2E:7D:0A:90:03:11:B4:79:B0:9A:6C:BC:F1:
  • 45:9C:F1:7B:1C:43:46