4 ms·
Unless you're creating [more than 20 new subdomains a week][1], you're not gonna hit that limit anyway. You can increase that figure to around 2,000 new subdoma
by Ajedi32 10y ago
Unless you're creating [more than 20 new subdomains a week][1], you're not gonna hit that limit anyway. You can increase that figure to around 2,000 new subdomains a week if you're willing to include multiple subdomains per certificate; that should be more than enough for all but the largest of sites.
And even if you do need more:
> If you are a large hosting provider or organization working on a Let’s Encrypt integration, we have a rate limiting form that can be used to request a higher rate limit.
[1]: https://letsencrypt.org/docs/rate-limits/ https://letsencrypt.org/docs/rate-limits/
- kuschku 10y agoIf you want to have a signup process that takes less than 9 hours, you have a max of 20 new subdomains a week. 20 users signing up a week - likely with a retention of a few percent - is not a "large hosting provider". You might have a few hundred users max, and already will be far over the rate limits.
- Ajedi32 10y agoJust start them off with HTTP and transparently upgrade to HTTPS after 9 hours. And if you're only retaining a small percentage of users who sign up, you can stretch that limit even further by only upgrading the users who you retain.
- Sephr 10y agoThis isn't possible in a properly deployed HTTPS site, since it would already have an HSTS header with includeSubdomains.