Domain > atw-api.atwoods.com

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

More information on this domain is in AlienVault OTX

Whois

Property	Value
NameServer	NS56.DOMAINCONTROL.COM
Created	1996-11-04 00:00:00
Changed	2014-11-03 00:00:00
Expires	2020-11-03 00:00:00
Registrar	GODADDY.COM, LLC

DNS Resolutions

Date	IP Address
2023-08-16	104.22.61.174 (ClassC)
2024-09-04	104.22.65.132 (ClassC)
2025-01-24	104.22.64.132 (ClassC)
2025-02-05	172.67.27.137 (ClassC)

HTTP/1.1 200 OKDate: Wed, 16 Aug 2023 01:20:59 GMTContent-Type: text/html; charsetutf-8Transfer-Encoding: chunkedConnection: keep-aliveCache-Control: privatevary: Accept-Encodingset-cookie: ASP.NET_Se

!DOCTYPE html>html langen xml:langen>head>    meta charsetutf-8 />    meta nameviewport contentwidthdevice-width />    link relshortcut icon typeimage/png href/Images/favicon.ico />    title>API | Multifront®/title>    link href/Content/css?vzEizMIOIHOL9VJK91OlCdIMjK5BUGX1s_JbC-hl_CWY1 relstylesheet/>/head>body>    div classpage>        header>            div classfloat-left>                p classsite-title>                    a href/>img src/Images/znode-logo.png altZnode />/a>                /p>            /div>            div classfloat-right>                nav>                    ul idmenu>                        li>a href/>Home/a>/li>                                            /ul>                /nav>            /div>            div classclear-fix>/div>        /header>        div idbody>    section>        h2>API Overview/h2>        p>The Znode API is organized around REST and is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. The API uses built-in HTTP features — such as headers, methods, and status codes — which can be understood by any off-the-shelf HTTP client. The Znode API only supports requests and responses in JSON format./p>    /section>    section>        h2>Authentication/h2>        p>The Znode API uses basic authentication with the strong>Authorization header/strong> to validate requests. An example of the format for the Authorization header is shown below:/p>        p>pre classcode>Authorization: Basic d3d3Lm15LXN0b3JlLmNvbXw1RDJCNEM1RS1EOEIzLTQ0ODgtOTA0RC02NDA5NDc2MkUxMzY/pre>/p>        p>The value after the word Basic is a Base64 encoded string that consists of a username and password separated by a pipe character (username|password), as described below:/p>        ul>            li>strong>Username:/strong> This is the domain name for the store whose data will be retrieved during the request (i.e. www.my-store.com)./li>            li>strong>Password:/strong> This is the API key for the domain, as found in the ZnodeDomai

View on OTX | View on ThreatMiner

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

Domain > atw-api.atwoods.com

Is this malicious?

Whois

DNS Resolutions

Port 443