# dwebs.to Web2 Bridge

{% hint style="info" %}
Note that the DWEB bridge works with all DWEB TLD and SLDs (subdomains). Though the site may take 10-20 seconds to load the first time it's visited to generate the proper SSL certificate.
{% endhint %}

The ultimate goal of Decentraweb is to exist across all browsers, networks, VPN's, and web3 applications without the end user installing or configuring anything. In the meantime we have the DNS Resolver, the incoming Browser Plugin, and JavaScript SDK. The dwebs.to bridge is another way you can share your web3 content with web2 users.\
\
Any A, CNAME, or IPFS content records you set on your TLD's or subdomains should be accessible via dwebs.to in the following example:\
\
DWEB domains examples:\
\
<http://sagan./> (IPFS content record set)\
\
dwebs.to bridge example:\
\
<https://sagan.dwebs.to/>\
\
If you have pinned a folder to IPFS you can also link directly to assets like so:\
\
<https://sagan.dwebs.to/image/record.jpg>\
\ <br>


---

# 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.decentraweb.org/decentraweb/learn/using-decentraweb-domains/dwebs.to-web2-bridge.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.