• Blog
  • Changelog
  • Roadmap
  • Pricing
  • FAQ
  • Getting started
    • Key concepts
    • Sign in
    • Create and switch organisations
    • Dashboard
  • Registers
    • Create and change a register
    • Upload and download entries
    • Add, edit and deactivate entries
    • Groups
    • Claims
    • Challenge codes
    • Connect and test an external register
    • Register activity
  • Membership definition
    • Add and order register assignments
    • Filters and outcomes
    • Preview before saving
    • Save and version history
  • Member code query
  • Members directory
    • Find a member
    • Look up the checks of a member code
    • Deactivate a membership
    • Anonymize a membership
  • Communities
    • Create, rename and delete a community
    • Filter by register, status, groups and claims
  • Frontends
    • Create a frontend
    • Frontend keys
    • Released claims
    • Sign-in settings
    • Guest access
    • Sign-in branding
  • Login with appsolut
    • Sign-up and onboarding
    • Sign-in and sign-out
    • Support requests
  • Frontend users
    • Find a frontend user
    • Membership and activations
    • Block a frontend user
    • Export a frontend user's data
    • Disconnect a frontend
  • Membership check
    • Check modes
    • Results and the check log
    • Rate limits
    • Grace rule
  • Vouchers
    • Partners
    • Create a voucher offer
    • Voucher pools
    • Activate, pause and end a voucher offer
    • Voucher settings
    • Import from the Portal
  • Redemptions
    • Handle a redemption
    • Redemption settings
  • Organisation settings
    • Organisation profile
    • Studio users and roles
    • Permissions
    • Billing
    • Roadmap and feature requests

appsolut ONE – enterprise community server. One platform for your internal and external communities, with membership and sign-in built in.

About
  • Blog
  • Contact
Documentation
  • Studio
  • Portal
  • Developers
Product
  • Roadmap
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Impressum

© Copyright 2026 appsolut ONE. All Rights Reserved.

  • Blog
  • Changelog
  • Roadmap
    1. Documentation
    2. Studio
    3. Membership check
    4. Rate limits
    Membership check

    Rate limits

    How the Studio stops people from guessing member codes and facts.

    Studio roles: "Owner" and "Administrator", and Studio users with a permission set that holds "Community: read" or "Community: manage", see refused checks in the check lookup. The limits are fixed: there is nothing to set.

    Without limits, someone could try member codes, names and birth dates until one fits. The Studio therefore counts failed checks and refuses further checks once a limit is reached.

    What counts as a failed check

    A failed check is a "Not valid" result in onboarding or eligibility mode, including "Valid, but outside the frontend's community".

    These do not count:

    • an "Unavailable" result, when a register could not answer;
    • a login check, as nobody types anything;
    • a check already refused as rate limited.

    A check still running counts as failed until it is logged, at most for 2 minutes. That way many checks sent at the same moment cannot all slip through before the first is logged.

    The limits

    Counted perLimit
    Member code5 failed checks in 15 minutes
    Applicant IP address a frontend forwarded (eligibility only)20 failed checks in 15 minutes, by default
    Frontend500 failed checks in an hour

    The windows slide: a failed check stops counting once it is older than the window.

    The limit per applicant IP address is a default. Where many applicants share one address, such as a company network behind a proxy, you can raise it for each frontend, up to 125 failed checks in 15 minutes: see Limits for applicants. The limit per member code and the frontend's 500 never change: the member code's limit protects each code against guessing.

    For the member code, the ways one code can be typed count as one code: variants that differ only in a leading plus sign or zeros, in case, in spaces, in invisible characters or in forms such as fullwidth digits. PQ-10017, pq-10017 and PQ-10017 share one budget. A separator still makes another code: PQ10017 is not PQ-10017.

    When a limit is reached

    The check is refused before any register is asked. The person sees that they should try again later; a frontend's backend gets the answer that it was rate limited. The check lookup shows the check as "Rate limited".

    A person who reached the member code's limit can try again after 15 minutes. If someone keeps failing, look up their member code in the check lookup: the reasons of the failed checks usually show what is wrong.

    Previous pageResults and the check logNext pageGrace rule