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 Thu, 20 Feb 2025 05:14:51 +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
      • R11
        • 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)
  • R11
validity period
Not valid before
2025-01-11
Not valid after
2025-04-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F9:1A:F9:06:BC:CF:6B:84:0B:58:C3:31:DC:7B:20:97:CD:BD:09:4C:3D:D3:D6:7A:A5:97:E6:E7:7B:49:CE:A7
SHA1
DD:9D:8D:4D:FE:C0:73:B6:E5:65:56:D4:B4:F0:B3:D1:F9:87:86:73
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:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Jan 11 06:24:08.999 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3D:61:93:99:6B:E1:08:02:69:04:50:E4:
  • 83:48:D0:E9:00:07:F3:A0:D7:56:B0:41:BC:0C:9F:A8:
  • 1F:DE:BB:FB:02:20:33:37:70:A3:29:31:BF:CE:EA:A9:
  • 68:E8:59:11:37:7B:57:D4:A9:35:32:2F:24:FC:3E:58:
  • 1F:7B:F2:AB:59:03
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jan 11 06:24:09.015 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:85:DF:19:F3:D8:4E:25:78:3C:7F:0B:
  • 27:BC:75:0B:42:2A:E4:AE:C6:3D:96:60:B6:E6:11:5B:
  • 76:ED:99:01:E5:02:20:4A:1C:D9:64:7C:97:13:BF:6C:
  • 8D:57:B9:84:F5:AA:C0:20:2B:E8:8A:D4:BB:79:1F:C1:
  • 14:04:A3:9B:19:14:F8