Security and scope

Clear boundaries for performance testing.

Automated scans and the standard audit target public websites and API endpoints. They are not permission to probe private systems or perform load testing.

What we test

Public URLs and endpoints submitted for point-in-time measurements, limited to returned network and HTTP timing evidence.

What is out of scope

Private databases, internal services, authenticated routes and load/stress testing are excluded unless separate scope and authorization explicitly permit them.

What to submit

Submit only public targets you are authorized to test. Do not submit passwords, API keys, access tokens or customer data in forms.

Contact information

Form submissions are sent to the site's existing lead-handling endpoint. Dedicated waitlist classification and a published retention schedule still need backend and policy review.

Responsible testing

Missing evidence is not poor performance.

A location with no completed measurement is reported as unavailable, not slow or healthy.

Read the methodology