# Rate Limit of dc-01.com **URL:** \ **Category:** Help\ **Created:** [December 14, 2016, 7:15pm UTC](https://community.letsencrypt.org/t/rate-limit-of-dc-01-com/24140 "2016-12-14T19:15:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dschuemann](https://avatars.discourse-cdn.com/v4/letter/d/dec6dc/32.png) [@dschuemann](https://community.letsencrypt.org/u/dschuemann)\ **Post date:** [December 14, 2016, 7:15pm UTC](https://community.letsencrypt.org/t/rate-limit-of-dc-01-com/24140/1 "2016-12-14T19:15:42Z")
Please fill out the fields below so we can help you better. My domain is: [dc-01.com](http://dc-01.com) I ran this command: certbot-auto standalone -d [dcloud-dna-apicem-rtp.dc-01.com](http://dcloud-dna-apicem-rtp.dc-01.com) It produced this output: My operating system is (include version): Linux 14.04 My web server is (include version): HA Proxy My hosting provider, if applicable, is: I can login to a root shell on my machine (yes or no, or I don’t know): yes I’m using a control panel to manage my site (no, or provide the name and version of the control panel):\ I’m trying to generate a certificate for my domain and by my calculation the rate limit should’ve expired yesterday. ---
**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\ **Post date:** [December 14, 2016, 7:49pm UTC](https://community.letsencrypt.org/t/rate-limit-of-dc-01-com/24140/2 "2016-12-14T19:49:01Z")
Do you own the domain `dc-01.com`, or just a specific subdomain that’s been given to you by a vendor or something like that? If it’s the latter, it’s possible that someone else has recently obtained more certificates for that domain Sites like [crt.sh](http://crt.sh) use Certificate Transparency log servers as their source, and Certificate Transparency is not a real-time mechanism; new certificates might not show up for a while (typically not much more than an hour, but it could be up to a day for most log servers). ---
**Author:** ![dschuemann](https://avatars.discourse-cdn.com/v4/letter/d/dec6dc/32.png) [@dschuemann](https://community.letsencrypt.org/u/dschuemann)\ **Post date:** [December 14, 2016, 7:53pm UTC](https://community.letsencrypt.org/t/rate-limit-of-dc-01-com/24140/3 "2016-12-14T19:53:47Z")
Yes I own the domain but it is used by multiple developers. Is the rate limit with just Lets Encrypt or any CA? ---
**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\ **Post date:** [December 14, 2016, 8:00pm UTC](https://community.letsencrypt.org/t/rate-limit-of-dc-01-com/24140/4 "2016-12-14T20:00:21Z")
This rate limit is specific to Let’s Encrypt. There’s a [form](https://docs.google.com/forms/d/e/1FAIpQLSfg56b_wLmUN7n-WWhbwReE11YoHXs_fpJyZcEjDaR69Q-kJQ/viewform?c=0&w=1) you can use to request an adjustment for the rate limits of your domain. I think you would need to use the same account key for all certificates with this solution. The approval process is manual and might take a few weeks. Since you mentioned this is for developers, depending on your use-case you could also look into using the staging server, which issues non-publicly-trusted certificates. The rate limits on that server are a bit more relaxed (I’m not sure if the specific rate limits are documented anywhere, though). The directory URL for the staging server is `https://acme-staging.api.letsencrypt.org/directory`. If you’re using `certbot`, you can switch to staging by adding `--staging` to the command. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [January 13, 2017, 8:00pm UTC](https://community.letsencrypt.org/t/rate-limit-of-dc-01-com/24140/5 "2017-01-13T20:00:32Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.