Appendix

The six chapters reduce to a few lists that belong beside the account register. This appendix collects them: one checklist for a new profile, one for the weekly review, a glossary and the tools worth bookmarking.

New-profile checklist

Run this list once for every new browser profile or cloud phone, before the first sign-in.

• Confirm the client's written permission and the platform's current account rules.
• Add a row to the register with the profile name, client and owner.
• Assign one dedicated proxy and label it with the profile name.
• Check the proxy's country, provider and network type with the proxy checker.
• Create the profile on a current engine version and save the fingerprint.
• Set timezone, language and location to follow the proxy's address.
• Open What Is My IP inside the profile and confirm the proxy's address appears.
• Run the WebRTC leak test inside the profile.
• Sign in once, with two-factor authentication on and backup codes held by the client.
• Store the password in the password manager, then close the profile and log the date.

What must agree

Most avoidable verification prompts trace back to two settings that disagree. The stack below lists what should tell the same story for a single account.

1 · Proxy addressCountry, city and network type.

2 · TimezoneThe zone that city actually uses.

3 · LanguageA language list that fits the country.

4 · Device claimOperating system, engine, fonts and graphics that belong together.

5 · Location settingsGPS and carrier details on a cloud phone.

6 · Account detailsBusiness address, phone number and payment country.

Weekly hygiene checklist

Fifteen minutes on a fixed day covers the list for a small agency.

• Compare the register with the tool: every profile has a row, and every row has a profile.
• Confirm each proxy is still assigned to one profile only.
• Spot-check two profiles for exit address and WebRTC behavior.
• Read the access log for unexpected openings or unfamiliar devices.
• Remove seats for anyone who left or changed clients.
• Shut down cloud phones left running and review metered time.
• Check for proxy expiry dates in the coming two weeks.
• Note any verification prompts or restrictions in the register.
• Delete profiles and release proxies for clients whose contracts ended.

Glossary

The terms below are used throughout the handbook. Definitions are kept to one line.

Term	Meaning
Antidetect browser	A browser that gives each profile its own fingerprint and storage
ASN	The number identifying the network that owns an IP address
Browser profile	One isolated identity: fingerprint, cookies, storage and proxy
Canvas fingerprint	A value derived from how a device draws a hidden image
Cloud phone	An Android device hosted by a vendor and controlled remotely
Cookie	A small file a site stores to remember a session
Dedicated proxy	An IP address assigned to a single customer
DNS leak	Name lookups that bypass the proxy and reveal the real network
Emulator	Software that simulates a phone on a desktop computer
Fingerprint	The combined device and browser traits a site can read
Mobile proxy	An IP address belonging to a mobile carrier
RPA	Recorded, no-code steps replayed inside a profile
Static ISP proxy	A fixed IP in a data center, registered to a consumer provider
Sticky session	A proxy setting that holds one IP for a set time
Two-factor authentication	A second proof at sign-in, such as an app code
WebRTC leak	A browser call feature exposing the real IP behind a proxy

ProxyLook tools and further reading

The three free tools linked in the first checklist cover most routine checks. The proxy checker reports country, ASN, provider and network type for an address. What Is My IP shows what a site sees from the current session. The WebRTC leak test looks for the real address behind a proxy.

For tools and deeper reading:

• The antidetect browser directory holds live details for the ten tools in chapter 5 and the rest of the list.
• The Proxy Playbook is the flagship book. It covers proxy types, protocols and buying decisions in depth.
• Scraping Without Blocks is the companion for data collection teams.

One reminder closes the book. Many platforms limit or forbid multiple accounts, and running them can breach terms of service. The operator carries that risk. These lists keep permitted accounts tidy. They do not prevent bans.

Key takeaways

• Every new profile gets the same ten checks before its first sign-in.
• Proxy address, timezone, language, device claim, location settings and account details should agree.
• A fifteen-minute weekly review keeps the register, seats and proxies accurate.
• The live directory and the two companion books hold the detail this handbook leaves out.