SSL-Tools

SSL check results of hosting.ip1.co.id

NEW You can also bulk check multiple servers.

Discover if the mail servers for hosting.ip1.co.id 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 Sat, 06 Mar 2021 01:59:43 +0000

We can not guarantee a secure connection to the mailservers of hosting.ip1.co.id!

Please contact the operator of hosting.ip1.co.id and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/hosting.ip1.co.id

Servers

Incoming Mails

These servers are responsible for incoming mails to @hosting.ip1.co.id addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
hosting.ip1.co.id
103.94.11.122
 -
supported
hosting.ip1.co.id
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.0
  • SSLv3
30 s
hosting.ip1.co.id
2401:3340::107
Results incomplete
- 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 @hosting.ip1.co.id address so far. Test mail delivery

Certificates

First seen at:

CN=hosting.ip1.co.id

Certificate chain
  • hosting.ip1.co.id
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • hosting.ip1.co.id
Alternative Names
  • hosting.ip1.co.id
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-06
Not valid after
2021-06-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B5:FB:92:29:1B:81:43:6C:F8:D4:7F:89:8A:19:1B:35:BA:85:26:71:F8:F2:C3:5B:70:15:C5:34:19:FB:63:F7
SHA1
75:C3:F1:62:40:65:93:3D:DE:B9:0A:2D:E6:96:FB:3C:CB:2E:9E:0F
X509v3 extensions
subjectKeyIdentifier
  • E4:43:19:D1:2D:C1:1E:50:34:3D:4E:0C:DD:F9:85:B9:AC:E9:BE:D3
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Mar 6 01:56:14.604 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F8:2D:D9:4F:89:8F:B4:AE:B7:A8:55:
  • BD:70:A7:93:4D:83:EE:AB:B6:32:E8:62:C9:B6:00:55:
  • F2:A2:F4:61:93:02:20:38:B0:94:1E:5A:6B:A8:A4:80:
  • 83:23:7A:EB:03:99:67:E1:B4:65:76:1A:0A:E1:B2:9C:
  • 62:67:93:7E:3B:FA:AF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Mar 6 01:56:14.642 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DF:10:6F:A4:51:BA:A4:C4:DC:B8:07:
  • 84:A6:1A:70:BE:87:F2:25:07:59:64:50:88:22:1A:83:
  • 86:41:82:71:67:02:20:53:5F:6D:DE:0B:53:83:1B:78:
  • DA:80:6C:9E:2D:28:2F:FB:C1:C5:80:A1:01:FB:AA:95:
  • E2:3C:7B:E4:AB:08:9A