Brand new browser profile
A browser that has never been used looks empty in many small ways.
A fresh profile starts with no cookies, empty storage, a history length of one, no earlier permission choices and no extensions. A person's browser rarely looks like that. Cloud browser agents often start from a clean profile each run, so they look like first time visitors. Saving and reusing a profile between runs makes the agent look like a returning visitor.
What it can and can't do
What the user does: Nothing. It reads defaults
It can
- See an empty history and storage
- Notice default permissions
- Treat a first visit differently when risk is high
- Reward a returning profile with fewer challenges
It cannot
- Tell a new person from an agent
- See other sites you visited
- Prove automation
- Read your real history
How it differs between platforms: New people and private windows also look fresh. Sites weigh it with other signals and give extra trust to a profile that keeps coming back.
Browser support
How a site asks for it
| API | history.length; document.cookie; localStorage.length; navigator.storage.estimate(); Notification.permission; navigator.permissions.query() |
| Browser compat keys | api.History.lengthapi.StorageManager.estimate |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Page reads history length and its own stored state
- Page may read quota and permission defaults
- Server notes there are no prior cookies or tokens
- Combined empty state raises the score for automation
Data you get
Shape: object
How often: per visit
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
history.length | integer | None | 1 in a new tab with no history | Not listed |
cookies | integer | None | 0 on a first visit | Not listed |
localStorage.length | integer | None | 0 on a first visit | Not listed |
permission states | list | None | all default; no past choices | Not listed |
Technical limits
- Also true for new devices and private windows
- Easy to fake with seeded storage
- Weak alone
The story
What it is
A used browser carries traces of its owner's life. A brand new one carries none, and sites notice the blank.
For you
You never see it. A new phone or fresh browser may get an extra check on first visit, which goes away as it is used.
For makers
Do not block fresh profiles on their own. Use them as one factor, and offer a clear sign in path. If you run agents, store and reuse a profile for the same site and keep it tied to one account.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A bank asks for more proof on a first visit from an empty profile. | None named |
| shopping | A store applies stricter checks to a checkout from a brand new browser. | None named |
| ads | An ad verifier counts empty profiles as lower trust. | None named |
| analytics | A site counts first visits using the lack of stored state. | Google Analytics |
| developer | An agent platform saves a profile so later runs look like returning visits. | None named |
| enterprise | A fraud team compares fresh profiles on sign up with later behavior. | None named |
Risks
- Penalizes new devices and private browsing
- Weak alone
What the platform says
- MDN: History.length. Docs describe how many entries are in the session history of the tab.
Good uses and abuse
Legitimate uses
- Fraud scoring
- Returning visitor trust
Known abuse
- Penalizing privacy minded users
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1.5 | Rough identifying entropy, when known |
Related capabilities
Related
- Private browsing detection. Can often tell if you are in a private window, until browsers close the gaps
- Storage quota estimate. Can see how much storage the site may use, which tracks your disk size
- Session cookies and tokens. Can keep you signed in between pages with a small ID stored in your browser
- Bot detection and CAPTCHA signals. Can combine many browser and network clues to guess if you are a bot
Sources
How well checked: Inferred from related behavior.