After many years of spotty availability and minimal support, we are excited to announce that the eth.link gateway is now powered by the eth.limo service.
eth.link is the original ENS gateway for dWebsite access, dating back to at least 2019. Initially developed and operated by the folks at ENS, it eventually found its way to Cloudflare, who has been operating it since early 2021 as part of a collaboration with the ENS team. With its eyecatching TLD (.link), it quickly became the standard for decentralized website connectivity.
However, over time eth.link became mired in legal controversies and developed a poor reputation for performance and service availability. Users were left frustrated over a lack of support and community engagement as well limited compatibility with the various decentralized storage protocols that house the static content necessary for creating and accessing websites built with ENS.
At eth.limo, we have been working diligently behind the scenes with the fantastic team at ENS Labs to identify a migration path and put eth.link on equal footing with eth.limo. As of now, the eth.link gateway is at feature parity with eth.limo, which means users and developers alike can now look forward to enjoying the following:
CCIP and ENSIP-10 support for wildcard resolvers and cross/off chain resolution of ENS domains.
Subdomain support
Technical support
IPFS, IPNS, Swarm, Arweave, and Arweave Naming Service (ARNS) compatibility
DNS over HTTPS
Continuous improvements
We are extremely excited to be a part of breathing new life into one of web3’s most prominent gateway services.
Thanks for the great service. Reporting an issue with resolving an ENS IPFS dWeb domain: atlantis-law.eth. The contenthash on-chain is correctly set to a CIDv1 (bafkreia3xhtwqovng6fadtu5s7ni4kumlmpcbzmqnqesfgearruscbfjle) which serves fine via ipfs.io and dweb.link (HTTP 200). But atlantis-law.eth.limo still returns HTTP 500 and even the generic /ipfs/<CID> path on eth.limo fails. Could this be a provider/pinning resolution issue on the eth.limo gateway side, and would you consider clearer error messages than a generic 500? Happy to share more diagnostics.