PLS.TO is a privacy-preserving PNS gateway for resolving Pulsechain Name Service (PNS) records and associated IPFS, IPNS or Skynet content (Web 3.0). PLS.TO allows users and dApp developers to effortlessly access and host static sites built with a combination of IPFS/IPNS/Skynet.
Why do we need PLS.TO?
The internet is becoming more controlled by a few big companies, which creates problems for a decentralized and open internet.
PLS.TO offers a solution by being a reliable alternative to the current system and giving people more control over the services they use. This will help the transition from the traditional internet (Web 2.0) to a decentralized one (Web 3.0).
How does PLS.TO work?
PLS.TO operates as a reverse proxy for PNS names and IPFS content.
Much like pls.fyi, PLS.TO uses a wildcard DNS record *.pls.to to dynamically capture requests for all PNS domains. The PLS.TO service automatically resolves the IPFS/IPNS/Skynet contenthash of the requested PNS record and returns the corresponding static content over HTTPS.
Since native IPFS/IPNS/Skeynet resolution capabilities are missing from the majority of browsers, PLS.TO represents a bridge from the “normal” internet to the decentralized one; by just adding .pls.to to your PNS name.
Zero-configuration is required in order to access or host a site or dApp on PLS.TO, making PLS.TO an excellent no-cost solution for providing Web 2.0 access to your project.
Security and Privacy
PLS.TO enforces strong origin isolation policies for all resources by default. Projects accessed through PLS.TO automatically receive security-hardened browser headers and all client data is encrypted with TLSv1.3 (default) or TLSv1.2 using the latest cipher suites.
All log data is fully anonymized, which prevents the ability to uniquely identify any single user.