#017Tutorial3 min
Analyze a website from its URL
Prove control of the exact domain, authorize the checks, and understand what a URL-based analysis can see.
Hackaiz team · updated 21/11/2026

01Start with the deployed website
A website address gives Hackaiz a target on the web, not access to the project that generated it. For example, https://app.example.com identifies a deployed application; it does not connect its GitHub repository or reveal its database settings. Use this entry point to examine the site as served over the network, then connect code or a database separately when that is the evidence you need.
Open Connect and choose “Analyse my infrastructure and projects”. Supply the address of the site or API you control. Read the detected target and check the hostname before continuing. A typing mistake can select a different host, and www.example.com is not the same proof scope as example.com. Do not submit a customer’s address merely because you built their site: technical control and permission to test are separate requirements.
03Review the selected work before launching
The interface offers automatic selection of compatible check families and a choice mode for adjusting them. Review what is selected rather than assuming every type of test applies to a URL. Unticked checks are neither run nor billed. Analyses use credits; use the confirmation information in the interface rather than guessing a cost from the number of pages on your site.
Quick mode checks visible elements such as headers, exposed files and visible configuration, and skips AI review. Deep mode adds compatible checks, AI review and non-destructive test requests. Neither mode bypasses domain proof. If you provide a test account for signed-in pages, use a dedicated account: the interface accepts a Cookie or Authorization header and limits its use to the displayed host. Never paste an administrator’s everyday session simply to increase coverage.
- 1Confirm the exact target and its verified authorization.
- 2Review compatible checks and any test-account option you intentionally enable.
- 3Read the confirmation summary, then use “Confirm and scan” only when the scope is correct.
04Read the findings within their actual scope
A URL analysis can reveal an exposed file or a missing protective header without proving anything about an unconnected repository. Conversely, a clean response from the website does not establish that database permissions are correct. Read each finding alongside its evidence and the checks that actually completed. Treat an unavailable check as a visibility limit, not as a passed test.
If the evidence points to source code, connect the authorized GitHub repository for code-level investigation. Where repository fixes are available, they are draft GitHub pull requests for a human to review and approve; Hackaiz does not merge them automatically. If you want continuing follow-up, monitoring is optional and applies only to connected systems. The first URL analysis is not a promise of continuous observation or complete security.
Frequently asked questions
Take the next step
Was this article helpful?