Domain > api.trakx.io

Welcome! Right click nodes and scroll the mouse to navigate the graph.

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2021-09-20	104.26.12.203 (ClassC)
2024-09-02	104.21.37.187 (ClassC)
2025-01-18	172.67.212.104 (ClassC)

HTTP/1.1 200 OKDate: Mon, 02 Sep 2024 18:14:25 GMTContent-Type: text/htmlTransfer-Encoding: chunkedConnection: keep-alivelast-modified: Thu, 01 Aug 2024 18:06:49 GMTaccess-control-allow-credentials: t

!DOCTYPE html>html langen>  head>      link hrefhttps://fonts.googleapis.com/css?familyPoppins relstylesheet>      meta charsetUTF-8>      meta http-equivX-UA-Compatible contentIEedge>      meta nameviewport contentwidthdevice-width, initial-scale1.0>      title>Trakx API/title>      style>        body {            font-family: Poppins;font-size: 18px;        }        code {          background-color: #eee;        }        .codeDiv {          background-color: #eee;          margin: 10px;          padding: 10px;          width: fit-content;        }        .comment {          color: #999;        }        /style>  /head>body>  h1>    Trakx Exchange Api  /h1>  h2>    Signing API requests  /h2>  p>Before calling private endpoint you will need to generate three headers/p>  li>code>X-Auth-Apikey/code> : the API key you have generated from the exchange UI./li>  li>code>X-Auth-Nonce/code> : the Unix time stamp, in milliseconds, used to generate the signature./li>  li>code>X-Auth-Signature /code> : HMAC-SHA256 signature digest, in hexadecimal form, of the concatenation of X-Auth-Nonce and X-Auth-Apikey signed by the Api Secret generated from the exchange UI./li>  p>and add them to your Http requests./p>    h3>Example values to test your code :/h3>    p>Please feel free to use the following values to test that your code is producing the correct signatures./p>    div classcodeDiv>    code>      i classcomment># Current unix timestamp in milliseconds/i>br/>      nonce  12345678789br/>      i classcomment># API Key generated using the exchange web application./i>br/>      api_key  abcdef1234br/>      i classcomment># API Secret generated using the exchange web application./i>br/>      secret  1234567abcdefbr/>      i classcomment># HMAC-SHA256 signature digest in hexadecimal representation./i>br/>      signature  HMAC.HexDigest(algorithm: SHA256, secret: secret, value: nonce + api_key)br />    /code>    /div>  /span>  p>With the above value, the signature is expected to be  br/>br/>code>4b617b1162ba00c892b960b49dca41dd7978dd

View on OTX | View on ThreatMiner

Data with thanks to AlienVault OTX, VirusTotal, Malwr and others. [Sitemap]

Domain > api.trakx.io

Is this malicious?

DNS Resolutions

Port 80

Port 443