# Clandestine Routing

As MASQ Network grows publicly, eventually there will be external forces who will want to intercept traffic or prevent the network from being utilized in the way it was intended - essentially attempt to censor or infiltrate the network itself

To operate in a way that allows the MASQ CORES packages to be routed with another security layer, [CORES packages](/masq/core-concepts/cores-packages.md) will be wrapped in a 'mask' - in some ways this will resemble 'onion routing'

The first mask is basic [Encryption Methods](/masq/core-concepts/encryption-methods-explained.md) seen today and they provide additional layers of security similar to typical HTTPS traffic we see today.

Long term development goals are on the ultimate security goal of creating **Clandestine routes** for CORES packages in the MASQ Network. In this type of route, each CORES package will be wrapped in a further layer of obscurity that will resemble different types of web traffic (not just HTTPS). Because traffic patterns viewed over time can be distinguishable (by methods such as Deep Packet Inspection) masking packages in random traffic patterns can deter typical packet sniffing and network traffic analyzation methods. This will prevent patterns from emerging and having requests and responses blocked against the users.

This entire layer will wrap around CORES packages and its various components before being handed off to other peers on the routing path.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.masqbrowser.com/masq/core-concepts/clandestine-routing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
