How it.you Works
How it.you works in your browser, on the server, and through editorial review.
it.you combines interactive IT utilities with guided practice and reviewed technical content. You can use most tools without creating an account. The sections below explain the important technical and editorial boundaries.
1. Choose a tool or workflow
Start with the task you need to finish
The tool directory groups utilities by task, while learning paths connect several tools into a repeatable workflow. Every learning step includes a concrete exercise and checkpoint rather than merely sending you through a list of pages.
2. Check where processing happens
Browser tools keep input on your device
Most formatters, converters, generators, timers, and image tools execute in your browser. Their page is labelled “Runs in browser,” and the value placed into the tool is not submitted to the it.you application server. You should still follow your organisation’s rules and avoid placing real secrets into a website unless you have independently verified the environment.
DNS Lookup, WHOIS Lookup, and IP Lookup need network data from outside the browser. Those pages send the requested domain or IP through the it.you server to a resolver, registry service, or IP-information provider. The result may therefore be subject to the relevant provider’s availability and data practices.
3. Understand saved and measured activity
Local progress and first-party events serve different jobs
The site stores saved-page shortcuts, recent pages, and learning progress in local browser storage. These conveniences remain on that browser and can be cleared through browser settings. A signed-in account can separately save favourite tools and use the support inbox. First-party engagement events record a page path and event category so broken or unused experiences can be identified; tool input is not included in those events.
4. Treat output as a starting point
Verify important results
Technical utilities can be affected by invalid input, browser limitations, changing external data, or implementation errors. Review the explanation and warnings on the page, follow the checks in our tool methodology, reproduce important results with an authoritative tool, and never treat a password meter, geolocation result, decoded token, or network lookup as proof on its own.
5. How articles reach the public site
Automation can assist, but a person must publish
Article ideas and drafts may be assisted by automation, but automation cannot publish them. A draft must pass structural checks and a human reviewer must verify sources, test examples, confirm original value, validate links, and choose an accountable byline. Articles that fail the public quality gate are excluded from archives, related links, direct article pages, and the article sitemap.
6. Accounts are optional
Sign in only when you need saved features
Accounts use Google OpenID Connect for sign-in. it.you requests the basic openid, email, and profile scopes; it does not receive your Google password or access to Gmail, Drive, contacts, or calendar. An account currently provides saved tools, editable profile fields, and a support inbox. It is not required for normal tool use.
7. Report a problem
Choose the right reporting path
Use Contact for a broken tool, factual correction, or account issue. Use Report Abuse for harmful activity and the Security page for a vulnerability. Include the exact URL, steps to reproduce the issue, and a non-sensitive sample when possible.