> For the complete documentation index, see [llms.txt](https://help.webhash.com/webhash-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.webhash.com/webhash-docs/faqs-on-decentralized-websites/how-are-decentralized-websites-different-from-traditional-websites.md).

# How are decentralized websites different from traditional websites?

Decentralized websites differ from traditional ones in the following ways:

1. 🌐 Hosting: Traditional websites use centralized servers, while decentralized ones distribute content across many nodes, improving resilience and availability.
2. 🛡️ Censorship: Centralized sites can be censored or taken down by authorities. Decentralized ones resist this as content is spread across many nodes.
3. 🏷️ Domain Names: Traditional sites use the Domain Name System (DNS), while decentralized sites use blockchain-based systems like Ethereum Name Service (ENS) for user-friendly names.
4. 🔒 Data Ownership: User data on traditional sites is often controlled by the website owner. Decentralized sites prioritize user control over personal data.
5. 🤝 Trust: Traditional sites rely on trust in centralized entities, while decentralized sites use blockchain technology to minimize trust in intermediaries.
6. 🗳️ Governance: Traditional sites are centrally controlled, while decentralized sites often use community-based decision-making models.

In short, decentralized websites offer a more resilient, secure, and democratic internet experience. 🌐💪


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.webhash.com/webhash-docs/faqs-on-decentralized-websites/how-are-decentralized-websites-different-from-traditional-websites.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.