Pornhub Never Asked My Age at Home—Then the Airport Wi-Fi Did

The age-verification screen appeared before the video page had finished loading. I was using the same Pornhub account that opened normally on my computer at home, yet the airport lounge wanted a face scan or another approved proof of age before showing my saved library. I assumed the account had forgotten my date of birth, so I signed out, signed back in, and reopened the page. The verification request returned. My flight was boarding in forty minutes, and I was trying to download one saved item rather than use expensive in-flight data.

The confusing part was not that an adult site requested proof of age.

It was that the request appeared only when I travelled.

At home in Bristol, I could open the same account without seeing it. I had completed an age check there months earlier and had barely thought about it since.

At Heathrow, the site behaved as though it had never met me.

I blamed the airport network first.

Then I blamed the account.

Neither explanation captured what had really changed.

Home had remembered more than my login

My home setup and travel setup looked almost identical from my side.

I had the same account.

I was using a laptop.

I opened the same website in a modern browser.

But the sessions were not the same.

At home, I used my personal computer in its normal browser window. It retained the site data created after my earlier verification.

At the airport, I was using a travel laptop in a private window. It carried none of that history and would erase the new session when I closed it.

Websites use cookies and related tokens to remember that a browser has signed in, accepted a preference, or completed a required step. (IETF)

My account knew who I was.

The travel browser did not carry the proof stored by the browser at home.

That explained why the age check appeared once. It did not explain why it kept returning after I completed it again.

For that, I had to look at what the airport connection was doing.

The verification was real—and so was the handoff afterward

Since July 25, 2025, services allowing pornography in the United Kingdom have been required to use highly effective age checks to prevent children from reaching the content. (Ofcom)

This was no longer a decorative “I am over eighteen” button.

It was a genuine access step.

I selected the available age-estimation method, followed the instructions, and received confirmation that the process had succeeded.

Pornhub reopened.

My library appeared.

I selected the saved item and started the download.

Then the airport Wi-Fi interrupted the connection and redirected the browser to its guest portal.

When internet access returned, Pornhub requested age verification again.

I had been away from home for less than an hour and had already completed the check twice.

The second request made the problem look like failed verification. In reality, the check had succeeded. What failed was everything that needed to remain connected afterward.

The Wi-Fi icon stayed full while the internet session expired

The lounge network showed full signal throughout the interruption.

That made the browser look guilty.

But the laptop was still connected only to the airport access point. Its permission to reach the wider internet had expired, so the guest portal needed to reopen before traffic could continue.

Travelers know the pattern: Wi-Fi appears connected, yet nothing loads until the hotel or airport login page is found again. (Reddit)

Once the portal renewed access, ordinary pages returned.

Pornhub returned too—but the journey no longer looked continuous. The verification had started before the interruption, while the next request arrived after the airport session had been rebuilt.

At home, the same connection could remain stable for days.

At the airport, it could change while I walked from the lounge to the gate.

That was why the issue appeared to follow me away from home. Travel combined a fresh browser with a network that repeatedly forgot the session underneath it.

My VPN was supposed to make that unreliable network safer.

Instead, the way it recovered created another break.

The trusted VPN kept giving me a fresh route

I had connected my regular VPN before opening Pornhub because I did not want a private browsing session travelling directly across airport Wi-Fi.

The provider was well established. It had polished applications, a large support operation, and an enormous server network.

Its automatic mode selected a fast London server.

When the airport portal interrupted the connection, the VPN recovered quickly by choosing another available route.

That was normally useful.

Here, it meant that I could complete verification through one exit address and return to Pornhub through another.

The age screen appeared again.

I turned off automatic selection and chose one London server manually.

The library opened.

I began the download.

Then I left the lounge, the laptop moved to another airport access point, and the VPN reconnected.

Pornhub asked for my age again.

I tried a second nearby server because it showed lower latency.

The page opened quickly.

It also restarted the verification flow.

The provider had plenty of servers and excellent speed. Neither quality preserved the result I had already earned.

The more aggressively it replaced a broken route, the more often I had to prove my age again.

Repeating the check became the privacy problem

By the third request, “just verify again” no longer sounded harmless.

The age-assurance service had already confirmed that I met the requirement. I did not want to repeat the same process every time an airport access point changed.

Ofcom’s research into age assurance has examined not only whether these systems work, but also how adults experience their privacy demands and repeated friction. (Ofcom)

My frustration was simpler than the policy debate.

I had already passed.

I needed the result to survive long enough to open the library and finish one download.

At that point, the comparison between VPNs changed.

I no longer cared which provider had more London servers or the lowest latency on the lounge Wi-Fi.

I needed one protected route that would stay coherent while the network beneath it changed.

The smaller app began with the travel problem

OnlydogVPN was installed on the laptop from an earlier test.

It had fewer server locations, a shorter public history, and fewer independent reviews than the provider I had been using. Those limitations were why it had remained a backup.

But the problem in front of me did not require another hundred locations.

It required one continuous session.

The smaller app opened with situation-based choices. I selected private browsing on weak or changing Wi-Fi.

It did not ask me to create a conventional email-and-password account before connecting. After an airport portal and three age checks, avoiding another registration screen was a welcome reduction in friction.

I tapped Connect.

Then I returned to Pornhub.

The age-verification screen appeared once more.

I completed it.

The library opened.

I selected the saved item and started the download.

Ten percent.

Twenty-eight.

Forty-six.

Then the lounge announced my gate.

The download survived the walk to the gate

I closed the laptop halfway and placed it in my bag without cancelling the download.

Outside the lounge, the Wi-Fi weakened and disappeared.

The laptop switched to my phone’s hotspot.

I expected the next browser refresh to bring back the age screen.

Instead, the download paused briefly and continued.

Fifty-two percent.

Sixty-eight.

The site remained signed in.

The verification remained accepted.

The smaller app uses an HTTP/3-based connection designed to recover when the underlying network changes. The practical result was immediate: the laptop moved from lounge Wi-Fi to mobile data without presenting Pornhub with an entirely new browsing journey.

The network changed.

The protected session stayed together.

Pornhub did not ask me to begin again.

The result mattered more than the protocol

I reached the gate with twelve minutes remaining.

The file was at 84 percent.

I placed the laptop on an empty seat and kept the phone beside it.

The progress bar reached 100 percent without another redirect, login, or age-verification request.

I opened the downloaded item briefly to confirm that it was available offline.

It played.

That completed the task that had started the investigation.

I did not need to prove that airport Wi-Fi was badly designed.

I did not need to identify every server the first provider had selected.

I needed one legitimate age check to remain useful while I moved through an unstable travel network.

The smaller app delivered that result.

“Away from home” was really three changes at once

The original question made it sound as though Pornhub trusted me at home and distrusted me when I travelled.

That was not what had happened.

At home, I used a browser that retained the earlier verification state on a stable connection.

Away from home, I used a fresh private session on a public network that repeatedly expired and changed underneath me.

The account was the same.

The adult using it was the same.

The session accompanying each request was not.

I could not observe Pornhub’s internal age-assurance rules or every routing decision made by either VPN. I could see the outcome: the established provider repeatedly restored internet access through fresh routes, while the smaller app carried one verified session from the lounge Wi-Fi to the phone hotspot and through to a completed download.

That was the difference that mattered.

The larger provider offered more servers and found fast replacements whenever the connection broke.

The smaller app prevented those replacements from repeatedly erasing the progress I had already made.

For age verification while travelling, continuity mattered more than the fastest nearby server.

Pornhub had not learned that I was away from home.

My home browser had remembered something the travel connection kept losing.