Domain > apidocs.localmed.com

More information on this domain is in AlienVault OTX

Whois

Property	Value
NameServer	NS-1394.AWSDNS-46.ORG
Created	2011-02-01 00:00:00
Changed	2014-12-02 00:00:00
Expires	2017-02-01 00:00:00
Registrar	GODADDY.COM, LLC

DNS Resolutions

Date	IP Address
2021-02-01	52.216.25.83 (ClassC)
2025-01-05	52.216.113.106 (ClassC)
2025-02-11	16.182.72.93 (ClassC)
2025-04-19	16.182.37.101 (ClassC)
2025-04-23	54.231.160.189 (ClassC)
2025-05-14	16.182.32.141 (ClassC)
2025-07-12	52.217.204.197 (ClassC)
2025-08-03	52.217.116.133 (ClassC)
2025-10-17	52.216.48.45 (ClassC)
2025-11-26	16.182.74.45 (ClassC)
2025-12-08	54.231.166.53 (ClassC)
2026-01-22	52.217.120.85 (ClassC)

HTTP/1.1 200 OKx-amz-id-2: E72SiNtMIQXX2RYUXxNQa9mt4GRoqD+zwdPajImFUxCoZyVjLPy1jaqzqTlqrR9YLFR/K5WNNScx-amz-request-id: BMWYVX0ZZ277SPAZDate: Sun, 05 Jan 2025 19:20:13 GMTx-amz-meta-s3cmd-attrs: uid:1

!DOCTYPE html>html langen>head>  meta charsetUTF-8>  title>localmed-internal/title>/head>body>  script srchttps://api.apiary.io/seeds/embed.js>/script>  script>    var embed  new Apiary.Embed({      apiBlueprint: FORMAT: X-1A
HOST: https://development.localmed.com

# LocalMed API (Production)

## Making a Request

### Content Type

##### Requests

Currently all endpoints support the `application/json` media type.

Content-Type: application/json

##### Responses

Response content types are specified using the `Accept` header. Currently we only support the JSON format:

Accept: application/json

### Encryption

We require all requests to be done over SSL.

### Encoding

UTF-8, *always*. Every string passed to and from the API needs to be encoded in UTF-8.

### Trailing Slash

All request paths should end in a trailing slash. If the requested path doesn	 end in a slash, an HTTP redirect is issued to the same URL with a slash appended. Note that the redirect may cause any data submitted in a POST request to be lost.

### Identify Your App

If possible, supply a `User-Agent` header with the name of your application and HTTP library you
e using, following the RFC 2616 format(http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.43):

GET /providers/
    User-Agent: my-application python-requests/2.4.3

### Example Request

$ curl --header User-Agent: my-application python-requests/2.4.3 --header Accept: application/json https://www.localmed.com/providers/?qBob

## Pagination

Resources that return multiple records will usually be paginated.

Pagination takes place through the use of the Link header as defined by RFC 5988(https://tools.ietf.org/html/rfc5988).

An example Link header for pagination:

Link: https://www.localmed.com/providers/?page1&perPage100>; relprev\n    https://www.localmed.com/providers/?page3&perPage100>; rel
ext\n
For pagination, we only use prev, next, first, and last rel types. Total number of records will be transmitted in the `X-Total-Count` header.

# Group IAM
# IA

Subdomains

Date	Domain	IP
pubsub.localmed.com	2025-10-27	52.9.63.130
email.localmed.com	2025-11-09	34.102.239.211
apidocs.localmed.com	2025-01-05	52.216.113.106
downloads.localmed.com	2023-10-30	16.182.108.121
adic-referrals.localmed.com	2025-10-12	3.169.173.10
assets.localmed.com	2024-05-19	18.161.6.116
qa.assets.localmed.com	2024-08-09	52.217.160.9
www.localmed.com	2023-11-01	3.92.97.76

View on OTX | View on ThreatMiner

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

Domain > apidocs.localmed.com

Is this malicious?

Whois

DNS Resolutions

Port 80

Subdomains