# Accessing The True Web

Access is one of the most important parts of the Veyra Protocol. Domains and hosting are only useful if people can actually reach them. Veyra is designed with **multiple entry points**, so even if one path is blocked, others remain open.

***

#### 4.1 Using Veyra Portals <a href="#id-4.1-using-veyra-portals" id="id-4.1-using-veyra-portals"></a>

Veyra Portals are **clearnet gateways** that resolve Veyra domains into websites.

* The **main Veyra Portal** is maintained by the core team.
* Anyone can run a **community mirror** of the portal.
* Mirrors are verifiable, each publishes a signed manifest so users know it’s authentic.

**How it works:**

* A user visits `myapp.veyra` or a mirror site.
* They enter a domain like `example.true`.
* The portal resolves the domain against the blockchain and fetches content from peer-to-peer nodes.

Portals make the true web accessible from any standard browser, no software installation required.

***

#### 4.2 Installing the Browser Extension <a href="#id-4.2-installing-the-browser-extension" id="id-4.2-installing-the-browser-extension"></a>

The Veyra Browser Extension brings native resolution of Veyra domains into Chrome, Firefox, and other Chromium-based browsers.

* **Adds `.anon`, `.true`, `.veyra` domains** to the browser’s address bar.
* **Directly queries the blockchain** for records.
* **Connects to peer-to-peer nodes** without going through centralized DNS.

**Benefits:**

* Lightweight, works in browsers people already use.
* Good for everyday users who don’t want a separate browser.
* Open-source, auditable, and community-maintained.

Extensions are the fastest way to bring `.veyra` domains into mainstream browsers.

***

#### 4.3 Veyra Browser Overview <a href="#id-4.3-veyra-browser-overview" id="id-4.3-veyra-browser-overview"></a>

The **Veyra Browser** is the most direct way to use the true web. Built on Chromium, it has native support for Veyra domains.

* Type `example.anon` or `myapp.veyra` directly in the bar, it just works.
* Automatically connects to healthy peer-to-peer nodes.
* Fallback options for mirrors and Tor if nodes are unavailable.
* Ships with privacy defaults: no trackers, no hidden logging.
* Fully open-source and forkable.

Unlike extensions, Veyra Browser doesn’t rely on Chrome or Firefox stores. It’s independent, censorship-resistant, and bulletproof by design.

***

#### 4.4 Tor Access <a href="#id-4.4-tor-access" id="id-4.4-tor-access"></a>

For maximum censorship resistance, Veyra domains are also reachable through a **Tor hidden service**.

* Provides access even in regions where clearnet portals are blocked.
* Protects user anonymity.
* Works seamlessly with the Veyra Browser or Tor Browser.

Tor ensures that the true web remains reachable even under heavy network-level censorship.


---

# 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.veyraprotocol.io/accessing-the-true-web.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.