France’s Age Check Kept Restarting Until I Stopped Changing Countries

The age check accepted me. The website did not.

I was at home in Lyon, using my personal laptop to open a legal adults-only site. A verification window appeared before the page loaded. That part was expected. I am over 18, and France now requires covered sites to do more than ask visitors to click a button promising they are adults.

What I did not expect was the loop.

I completed the third-party check, received confirmation and returned to the original tab. Instead of opening the page, the site displayed a location mismatch message and sent me back to the beginning.

I blamed the verifier and repeated the process.

Same result.

Only then did I remember that my regular VPN was connected to Belgium. I had chosen Brussels because it was nearby and I did not want my French internet provider seeing which site I was visiting.

I switched to Switzerland and tried again.

The verification page loaded, paused and expired. My next attempt ended with another mismatch.

By that point, I had proved my age twice and gained access zero times.

The age check was asking one question; my VPN was creating another

France’s age-verification rules require covered adult sites to prevent minors from entering rather than relying on a simple declaration of age. In June 2026, the Court of Justice of the European Union confirmed that France can impose age-verification requirements on relevant services established elsewhere in the EU, within the conditions set by European law. (Europa)

For adults, that shifted the practical question. The checks were not likely to disappear. The real concern was how to complete one without revealing more information than necessary.

French regulators favour a structure that separates proof of adulthood from browsing identity. An independent provider confirms that the user is an adult, while the content site receives the result rather than a complete identity. Under the intended “double anonymity” model, the site should not know who the visitor is, and the verifier should not know which adult site is being accessed. (Cnil)

That privacy separation also explains why the process involves several moving parts.

The original site starts a verification session. A third party confirms adulthood. The browser then carries that confirmation back to the first site. The handoff works best when every stage still looks like part of the same visit.

My VPN kept framing the problem as a country choice. The age-check flow needed continuity.

Changing an IP address does not reset the browser. Cookies, session data and previous account information remain in place. Jumping from France to Belgium and then Switzerland can therefore make a session less coherent rather than more private. (Wired)

A brief public discussion captured the same practical mistake: changing the VPN location did not remove the prompt because the rest of the session still carried its original context. (Reddit) That was exactly what I had overlooked.

A larger map gave me more ways to restart

My established VPN had been the obvious first choice.

It had a long public history, a large support operation and servers across Europe. When Belgium produced a mismatch, I could try Switzerland, the Netherlands, Germany or France within seconds.

That flexibility felt useful until every new choice restarted the process.

I disconnected from Belgium and opened the site through Switzerland. When the verification page hesitated, the VPN reconnected. The app still displayed Switzerland, but the verification session had already expired.

I tried a French server next, assuming that matching my physical country would solve the problem. The correct French verification flow appeared, but the return from the third-party check stalled.

Ordinary browsing still worked. Speed tests looked normal. The failure was narrower: one multi-step verification session could not reach the end without being interrupted or contradicted by another location change.

I could not inspect the website’s or verifier’s internal filtering and location rules, so I cannot identify the exact signal behind each rejection. The visible pattern was enough. Every server change created another address, another session attempt and another opportunity for the two sides of the process to disagree.

That was the point when I stopped trying to look foreign.

I did not need to appear Belgian, Swiss or Dutch. I needed one private connection to remain stable long enough for the verifier to say “adult” and for the original site to accept the answer.

One route through the entire check

I opened OnlydogVPN.

Instead of beginning with a country map, I selected the privacy-oriented browsing situation. The smaller app established the route without asking me to compare nearby locations.

I closed the failed tabs and began again from the original page.

The verifier opened. I completed the available privacy-preserving age check. It confirmed that I was over 18 and returned me to the site.

This time, the page opened.

No location warning. No expired return. No fourth request to prove the same fact.

The important result appeared before any technical explanation: the same route stayed active while the browser moved from the adult site to the independent verifier and back again.

That was the comparison standard I had missed.

The service uses an HTTP/3-based transport with additional traffic obfuscation. In practice, it is built to keep the connection usable through brief network disruptions without presenting the most familiar pattern of a conventional VPN tunnel.

The age-check flow did not need another country. It needed the connection to remain coherent while several pages passed one proof between them.

I tested the result once more after moving the laptop from home Wi-Fi to my phone’s hotspot. The service recovered without asking me to choose a new location. The completed age proof remained accepted, and the page reopened normally.

I had started the evening believing that location was the lever. Stability was the lever.

Privacy did not require avoiding the age check

Using a VPN around age verification is easily confused with trying to evade the check itself. That was not what solved the problem.

France wants covered sites to keep minors out. Regulators also recognise that location alone is unreliable because people can use VPNs, which is why a French IP address—or the lack of one—cannot establish adulthood by itself. (Cnil)

For an adult concerned about privacy, the choice is not simply “upload identity directly to the site” or “pretend to live abroad.”

The better approach is to give each tool one job.

The independent verifier establishes adulthood.

The adult site receives the result rather than a complete identity.

The VPN protects the connection carrying that process.

Once I separated those tasks, the setup became easier to judge. The VPN did not need to replace age verification. It needed to protect the session and stop it from collapsing during the handoff.

That is also why the smaller app’s anonymous basic use mattered. I was already entering a sensitive browsing context involving a verification provider. I did not want to add another email address, password and permanent account simply to protect the traffic around it.

The service let me connect without creating that extra identity trail.

It was a small design decision, but it matched the problem better than a large server map. I needed less account-building and more continuity.

What appeared after the page opened

Once access worked, I opened the site’s privacy information and then the CNIL guidance explaining double anonymity.

That was when I noticed the blocked-request counter rising.

Advertising and tracking requests were being stopped as I moved between pages. The completed age proof still worked, but unrelated background requests were reduced.

That smaller discovery addressed the concern that had sent me to a VPN in the first place.

Age verification concerns one sensitive fact: whether a person is an adult. It should not become an excuse for every advertising company embedded on the page to collect more information about the visit.

The CNIL’s approach is based on data minimisation—proving the required fact without unnecessarily exposing the person behind it. (Cnil) A connection that also reduces background tracking follows that principle more naturally than repeatedly changing countries and hoping the verification screen disappears.

The limitation was visible on the map

The smaller service has fewer server locations, a shorter public history and fewer independent reviews than the established provider I tried first.

Someone who regularly needs a specific national endpoint may still prefer a larger network. A privacy service also builds trust over time, and a shorter history offers less external evidence to examine.

Neither limitation affected the task that had failed.

My regular provider offered more countries than I needed, yet its interface kept presenting the problem as a geographical choice. Each new server invited another restart.

The smaller app offered fewer location decisions but preserved the one session that mattered.

A free option would have introduced another round of trial and error, likely through heavily reused addresses, while the verification process continued expiring in the background. The urgent problem was not the subscription price. It was completing the check once without scattering the session across several locations.

France’s age-verification system was asking me to prove one fact without disclosing my whole identity.

The successful VPN setup followed the same logic. It did not invent a foreign persona. It carried one private, consistent session from the age prompt to the proof and back to the page.

For a French age-check mismatch, keeping the session coherent matters more than changing the country beside the connect button.