# Getting 429 rate limit on domain with less than 20 certs in past week

**URL:** <https://community.letsencrypt.org/t/getting-429-rate-limit-on-domain-with-less-than-20-certs-in-past-week/68703>\
**Category:** Help\
**Created:** [August 7, 2018, 12:37am UTC](https://community.letsencrypt.org/t/getting-429-rate-limit-on-domain-with-less-than-20-certs-in-past-week/68703 "2018-08-07T00:37:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![heng](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/heng/32/25304_2.png) [@heng](https://community.letsencrypt.org/u/heng)\
**Post date:** [August 7, 2018, 12:37am UTC](https://community.letsencrypt.org/t/getting-429-rate-limit-on-domain-with-less-than-20-certs-in-past-week/68703/1 "2018-08-07T00:37:32Z")

</div>

This is for domain yale.edu

Based on crt.sh, we’re not seeing that we are definitely below the rate limit on certs issued for that domain - [https://crt.sh/?q=%.yale.edu](https://crt.sh/?q=%25.yale.edu)

However, we’re getting a 429 error when we are attempting to issue a cert for a subdomain on yale.edu using letsencrypt-express v2.0.5 :

```
2018-08-07 00:11 +00:00: { type: 'urn:acme:error:rateLimited',
  detail: 'Error creating new cert :: too many certificates already issued for: yale.edu: see https://letsencrypt.org/docs/rate-limits/',
  status: 429 } 

```

Any ideas?

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [August 7, 2018, 12:53am UTC](https://community.letsencrypt.org/t/getting-429-rate-limit-on-domain-with-less-than-20-certs-in-past-week/68703/2 "2018-08-07T00:53:10Z")

</div>

crt.sh has been backlogged recently. It probably has an incomplete picture of certificates issued in the last week.

Google’s CT search site should be more up-to-the-minute but it’s harder to work with:

[https://transparencyreport.google.com/https/certificates?cert\_search\_auth=&cert\_search\_cert=&cert\_search=include\_expired:false;include\_subdomains:true;domain:yale.edu;issuer\_uid:4428624498008853827&lu=cert\_search](https://transparencyreport.google.com/https/certificates?cert_search_auth=&cert_search_cert=&cert_search=include_expired:false;include_subdomains:true;domain:yale.edu;issuer_uid:4428624498008853827&lu=cert_search)

---

<div class="post-metadata">

**Author:** ![heng](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/heng/32/25304_2.png) [@heng](https://community.letsencrypt.org/u/heng)\
**Post date:** [August 7, 2018, 3:52am UTC](https://community.letsencrypt.org/t/getting-429-rate-limit-on-domain-with-less-than-20-certs-in-past-week/68703/3 "2018-08-07T03:52:32Z")

</div>

Thanks mnordhoff, I’ll work with that instead and see if I can figure out where these certs are issued from

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [August 7, 2018, 9:38pm UTC](https://community.letsencrypt.org/t/getting-429-rate-limit-on-domain-with-less-than-20-certs-in-past-week/68703/4 "2018-08-07T21:38:38Z")

</div>

Also, universities can often get a Let’s Encrypt rate limit increase relatively easily, so you might also want to get in touch to request that the rate limit be increased.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 6, 2018, 9:38pm UTC](https://community.letsencrypt.org/t/getting-429-rate-limit-on-domain-with-less-than-20-certs-in-past-week/68703/5 "2018-09-06T21:38:58Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.