SSL-Tools

SSL check results of smsmasking.id

NEW You can also bulk check multiple servers.

Discover if the mail servers for smsmasking.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 Fri, 01 Aug 2025 08:31:55 +0000

We can not guarantee a secure connection to the mailservers of smsmasking.id!

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

/mailservers/smsmasking.id

Servers

Incoming Mails

These servers are responsible for incoming mails to @smsmasking.id addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smsmasking.id
103.146.203.49
Results incomplete
0
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
12 s
mail.otpcode.id
202.74.239.242
 10
supported
otpcode.id
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=otpcode.id

Certificate chain
  • otpcode.id
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • otpcode.id
Alternative Names
  • otpcode.id
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-27
Not valid after
2025-09-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
53:15:7A:EA:06:E2:09:B0:9E:96:0D:FF:B1:0B:6B:58:FA:18:32:CF:9F:82:7E:16:2D:F6:C1:32:72:D1:3C:B4
SHA1
23:B4:46:1F:9B:00:43:09:3D:C6:D9:4F:B2:DD:54:5E:7A:8F:F7:3C
X509v3 extensions
subjectKeyIdentifier
  • 89:43:3D:2F:B5:BD:E9:F5:E8:E4:67:A2:40:AA:07:E1:5C:26:26:29
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/61.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Jun 27 17:31:14.961 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2C:5F:29:BC:7F:17:E3:85:9E:1F:93:A3:
  • BD:BC:3E:65:38:5C:2D:00:D4:D4:5E:86:6A:0D:0E:D6:
  • B4:88:CC:73:02:20:56:E0:17:23:93:AB:AB:83:2A:7E:
  • 91:4C:A7:CD:5F:6F:04:EF:5E:AE:30:69:45:B7:C6:93:
  • 66:FE:BC:29:18:26
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jun 27 17:31:16.966 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:DD:B6:36:0E:75:6A:F9:B3:25:FA:EA:
  • 8F:D9:12:B4:34:B3:C0:6C:EF:73:F3:4B:61:79:FF:82:
  • 8E:39:5F:45:32:02:21:00:CB:81:DD:A8:AA:43:E8:49:
  • C5:D1:07:A1:CE:48:58:64:62:A2:80:DC:50:8B:77:1D:
  • 62:37:0B:C2:1A:E2:25:EF