# New rate limit question **URL:** \ **Category:** Uncategorized\ **Created:** [March 26, 2016, 3:35am UTC](https://community.letsencrypt.org/t/new-rate-limit-question/13210 "2016-03-26T03:35:17Z")\ **Posts on this page:** 1\ **Showing post:** 20
**Author:** ![xrobau](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/xrobau/32/6762_2.png) [@xrobau](https://community.letsencrypt.org/u/xrobau)\ **Post date:** [April 15, 2016, 4:16am UTC](https://community.letsencrypt.org/t/new-rate-limit-question/13210/20 "2016-04-15T04:16:32Z")
> [@jsha](#): > > Close. I'm saying that the Certificates/Domain rate limit (the one most people hit) is for new sets of hosts. That sounds like I am totally wrong about the rate limits then. Which _does_ make sense, because my interpretation just seemed flawed. So, if I may just clarify, with another contrived example (Sorry!) Lets say I've decided that Route53 is charging too much at 50c/domain, and I'm going to give away DNS hosting for nothing, but make it up in volume. To do this, I'm going to need a bunch of nameservers, and a bunch of machines. Because I like scalability, I deploy one new machine per day, with the FQDN of {{random uuid}}.superawesomedns.com, but because I can't write APIs, every host needs to expose a https service to the end user. I use the standard letsencrypt client, and http auth, to get a unique key and cert per host. That then has a cronjob that renews the cert whenever required. Because I'm not hitting the 20 hosts per week, that should be fine? Or, am I going to hit another rate limit somewhere. Re-reading your original post, in the other thread > [@Rate Limits for Let's Encrypt](https://community.letsencrypt.org/t/rate-limits-for-lets-encrypt/6769/2): > > Added an exception to this limit for renewing certificates (issuing a new certificate with same names as a previous one). That's obviously where my disconnect happened. --- _[View the full topic](https://community.letsencrypt.org/t/new-rate-limit-question/13210)._