# Gateway Basics

### Requirements

To use the eth.limo gateway, you need to have an ENS domain with a valid resolver and a supported `contenthash` record. Wildcard resolvers conforming to the [ENSIP-10](https://docs.ens.domains/ensip/10/) standard are supported. Just append `.limo` to the end of any `.eth` or `.gno` domain to serve your dWebsite content.

### CCIP and Off-chain Resolution

The `*.eth.limo`, `*.eth.link`, and `*.gno.limo` gateways support off-chain resolution via [CCIP](https://eips.ethereum.org/EIPS/eip-3668). For more information, please consult the following resources:

* [Unruggable Gateway](https://github.com/unruggable-labs/unruggable-gateways)
* [Cross Chain/Offchain Resolvers](https://docs.ens.domains/resolvers/ccip-read)

### Caching

By default all content is cached for 5 minutes. This means that if you update the `contenthash` of your ENS domain, it *may* take *up to* 5 minutes for those changes to become visible. We are actively working on a refactor of the caching layer which will eventually deprecate this limitation.

### HTTPS Certificates

All subdomain certificates, i.e. non `*.eth.limo` are generated on demand, provided that there is a valid resolver and `contenthash` record set for the subdomain. Users no longer need to request certificates manually in our [Discord server](https://discord.gg/zf8NxW94rB).

### Server Side Headers

If you require custom HTTP response headers to support features such as [SharedArrayBuffer](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer) please contact us in [Discord](https://discord.gg/zf8NxW94rB). We are actively collaborating on an ENSIP specification that will allow ENS domain holders to specify server side headers in a `TXT` record, however this feature is still in heavy development for the time being.

### Supported Storage Protocols

Currently, we support IPFS, IPNS, Arweave, ARNS (Arweave Name System), and Swarm.