SSL-Tools

SSL check results of hi2.in

NEW You can also bulk check multiple servers.

Discover if the mail servers for hi2.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 Mon, 27 Jul 2026 23:44:24 +0000

The mailservers of hi2.in can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.hi2.in
2a01:4f8:c2c:e15a::1
 0
supported
checker.in
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.hi2.in
142.132.163.249
 0
supported
checker.in
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 @hi2.in address so far. Test mail delivery

Certificates

First seen at:

CN=checker.in

Certificate chain
  • checker.in
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R13
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • checker.in
Alternative Names
  • *.checker.in
  • *.hi2.in
  • *.telegmail.com
  • checker.in
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R13
validity period
Not valid before
2026-05-13
Not valid after
2026-08-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
15:80:92:4A:FF:15:46:1B:DF:D1:F1:D8:F0:65:29:66:22:10:68:F9:5D:6C:31:CB:97:7F:FA:29:C0:11:53:04
SHA1
01:AA:4A:86:90:40:EB:0F:3C:71:7F:9D:91:C0:3C:76:7E:9D:66:44
X509v3 extensions
subjectKeyIdentifier
  • 30:80:B8:0A:27:59:08:9A:D8:99:36:1F:26:C7:96:09:AD:B3:B7:56
authorityKeyIdentifier
  • keyid:E7:AB:9F:0F:2C:33:A0:53:D3:5E:4F:78:C8:B2:84:0E:3B:D6:92:33
authorityInfoAccess
  • CA Issuers - URI:http://r13.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r13.c.lencr.org/67.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 26:E3:64:6E:58:69:21:23:BC:34:3F:47:24:35:9B:37:
  • 92:CD:24:5A:88:D8:15:D3:93:33:FD:99:18:AB:47:23
  • Timestamp : May 13 14:44:13.544 2026 GMT
  • Extensions: 00:00:05:00:10:BE:DA:E5
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C8:67:CD:80:CD:82:D2:32:BD:15:71:
  • 77:18:03:2E:CB:02:B0:30:03:CD:82:17:A5:64:8E:B3:
  • E7:E7:7C:06:D6:02:21:00:AB:62:DD:EF:8C:52:CC:2E:
  • 89:82:11:FA:0A:F4:9E:01:59:B6:15:77:20:8C:BE:8E:
  • 1D:A7:31:A9:4A:37:FC:96
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AF:67:88:3B:57:B0:4E:DD:8F:A6:D9:7E:F6:2E:A8:EB:
  • 81:0A:C7:71:60:F0:24:5E:55:D6:0C:2F:E7:85:87:3A
  • Timestamp : May 13 14:44:14.373 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:06:98:9B:72:50:40:CA:B9:F2:3D:7B:50:
  • 9A:64:5D:88:63:7D:85:91:70:39:FB:87:A2:89:7B:6D:
  • 2B:D2:3E:C5:02:21:00:EA:75:A2:01:61:A1:A5:32:16:
  • 43:4B:7E:3D:D2:4E:4D:7A:4F:27:AE:71:4B:98:9A:2D:
  • EB:C2:D8:83:8A:37:B4