# See cmd/shell.go for definitions of these rate limits.
totalCertificates:
  window: 2160h
  threshold: 100000
certificatesPerName:
  window: 2160h
  threshold: 2
  overrides:
    ratelimit.me: 1
    # Hostnames used by the letsencrypt client integration test.
    le.wtf: 10000
    le1.wtf: 10000
    le2.wtf: 10000
    le3.wtf: 10000
    nginx.wtf: 10000
  registrationOverrides:
    101: 1000
registrationsPerIP:
  window: 168h # 1 week
  threshold: 3
  overrides:
    127.0.0.1: 1000000
pendingAuthorizationsPerAccount:
  window: 168h # 1 week, should match pending authorization lifetime.
  threshold: 3

# See cmd/shell.go for definitions of these rate limits.
totalCertificates:
  window: 2160h
  threshold: 100000
certificatesPerName:
  window: 2160h
  threshold: 2
  overrides:
    ratelimit.me: 1
    # Hostnames used by the letsencrypt client integration test.
    le.wtf: 10000
    le1.wtf: 10000
    le2.wtf: 10000
    le3.wtf: 10000
    nginx.wtf: 10000
    good-caa-reserved.com: 10000
    bad-caa-reserved.com: 10000
  registrationOverrides:
    101: 1000
registrationsPerIP:
  window: 168h # 1 week
  threshold: 3
  overrides:
    127.0.0.1: 1000000
pendingAuthorizationsPerAccount:
  window: 168h # 1 week, should match pending authorization lifetime.
  threshold: 3

Add CAA test domains to rate limit policies.
Add CAA test domains to rate limit policies.

This ensures that repeatedly running the integration test locally doesn't run
afoul of rate limits.
