Domain > decisia-api.lexum.com

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2024-11-24	15.157.24.0 (ClassC)
2024-12-26	3.97.34.175 (ClassC)
2025-05-01	15.223.22.214 (ClassC)
2025-05-05	15.157.231.203 (ClassC)
2025-05-14	15.222.77.191 (ClassC)
2025-05-17	15.156.157.164 (ClassC)
2025-06-09	35.182.34.52 (ClassC)
2025-07-17	15.157.203.67 (ClassC)
2025-07-31	15.157.224.203 (ClassC)

HTTP/1.1 200 Date: Sun, 24 Nov 2024 14:57:59 GMTContent-Type: text/html;charsetUTF-8Content-Length: 3077Connection: keep-aliveserver: Apachestrict-transport-security: max-age63072000; includeSubDomain

!DOCTYPE html>html langen>head>    meta charsetUTF-8>    meta namerobots contentnoindex, nofollow, noarchive, noimageindex>    title>Decisia Api Documentation/title>    link relstylesheet typetext/css hrefcss/swagger-ui.css/>    link relstylesheet typetext/css hrefcss/index.css/>    link relstylesheet typetext/css hrefcss/decisia.css/>    link relicon typeimage/png hrefimages/favicon-32x32.png sizes32x32/>    link relicon typeimage/png hrefimages/favicon-16x16.png sizes16x16/>/head>body>div classdecisia-header>  div classdecisia-header-wrapper>    a hrefhttps://decisia.lexum.com/>        img srcimages/decisia_by_lexum.png altDecisia by Lexum>    /a>  /div>/div>div classdecisia-info>    h2>API Access Notes/h2>    ul>        li>The API is only accessible using a secure HTTP connection            (HTTPS).        /li>        li>The API Key is your access token to use the service. It must            be sent using the request parameter "apiKey" in each of            your requests.        /li>        li>The current installation is a test setup which means that            you can use the API freely to add and modify documents.        /li>        li>The URL, Client ID and API Key will be different on your            production installation of the API so make sure it is easy for you            to change these in your code.        /li>    /ul>    h2>API Usage Notes/h2>    ul>        li>The JSON Objects are em>unordered/em> which means that the            order of the various fields may change.        /li>        li>If a query to the API returns several Objects, the result is            also em>unordered/em>, which means that several identical calls            will yield the same results but not necessarily in the same order.        /li>        li>Optional fields that are empty will not appear in a JSON            Object when getting them from the API.        /li>    /ul>    h2>API Calls vs. Admin Labels/h2>    p>You might have noticed that the API calls in the different        documentation pages do not match the

Subdomains

Date	Domain	IP
decisia.lexum.com	2024-11-10	15.157.150.45
eliisa.lexum.com	2024-11-24	15.222.180.220
scc.lexum.com	2024-11-24	15.157.24.0
decisia-waperc.lexum.com	2025-01-03	52.60.61.59
csc.lexum.com	2024-11-24	15.157.24.0
scc-csc.lexum.com	2024-11-24	15.157.24.0
decisia-fja-cmf.lexum.com	2024-11-24	3.97.167.5
decisia-api.lexum.com	2024-11-24	15.157.24.0
scc-csc-api.lexum.com	2024-11-24	3.97.167.5
decisia-demo-api.lexum.com	2024-11-24	15.157.24.0
qweri.lexum.com	2024-11-24	52.60.119.100
scc-csc-qweri.lexum.com	2024-11-24	15.222.180.220
zoupio.lexum.com	2024-11-24	15.222.180.220
decisia-demo.lexum.com	2024-11-24	3.97.167.5
qweri-demo.lexum.com	2024-11-24	52.60.119.100
ccq.lexum.com	2024-11-24	52.60.119.100
www.lexum.com	2024-12-26	143.110.211.198

View on OTX | View on ThreatMiner

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

Domain > decisia-api.lexum.com

Is this malicious?

DNS Resolutions

Port 80

Port 443

Subdomains