curl against three VPN pricing pages: one clean read, one trap, one 403
I keep a Black Friday VPN price page up to date by hand, and "by hand" was getting old: three providers, prices that change during the sale, and a rule I hold myself to, which is that every price on the page carries the
I keep a Black Friday VPN price page up to date by hand, and "by hand" was getting old: three providers, prices that change during the sale, and a rule I hold myself to, which is that every price on the page carries the date it was read on the provider's own page. So tonight (16 November 2026, around 19:50 Paris time) I tested how far plain curl gets on each pricing page. Three providers, three different behaviours.
The probe
UA="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0 Safari/537.36"
curl -sL -m 25 -A "$UA" -H "Accept-Language: en-US" -o page.html \
-w "%{http_code} %{size_download} %{num_redirects}\n" "$URL"
grep -o '[$€][0-9]\+\.[0-9][0-9]' page.html | sort | uniq -c | sort -rn
Nothing clever: follow redirects, send a browser User-Agent, then count every currency amount in the HTML.
Proton VPN: everything is in the HTML
200, 191,159 bytes, and the amounts come out clean:
4 $9.99
4 $12.99
1 $2.49
1 $59.76
1 $83.88
1 $6.49
1 $77.88
1 $119.88
Each billed amount appears exactly once, next to the strings first 24 months and every 12 months. That maps to a complete offer without opening a browser: VPN Plus at $2.49 a month, billed $59.76 for the first 24 months, then $83.88 every 12 months, and Unlimited at $6.49 a month, billed $77.88 for the first year, then $119.88.
One thing I checked because I expected it to bite: sending Accept-Language: de-DE from my server returned the same dollar amounts, same byte count. The currency follows something other than the language header (the provider says prices are shown for your country at checkout), so a price read this way is "the price shown to my server's location", and the page has to say so.
Surfshark: the prices are there, and so are numbers you must not publish
200, 276,314 bytes. The amounts I was looking for are present: €2.49 six times, €3.99 three times, €67.23 four times, €107.73 twice. But the same grep also returns €511.65 and €538.65.
Those are not what anyone is billed for the plans in the cards. A regex that takes "the largest amount near the plan name" would have published a price seven times too high, with a date and a straight face. The fix is boring: an amount only counts if it sits in the same text block as its billing sentence ("for the first 27 months"), and anything unmatched is dropped and logged, never guessed.
NordVPN: no page at all
403, 5,585 bytes, <title>Just a moment.... A bot challenge, before any price. I am not going to work around a challenge to scrape a price, so the rule on my page is simple: the NordVPN line keeps its last successful reading (14 November) with that date printed next to it, and a note saying the 16 November reading is missing.
What I took away
| Provider | HTTP | Prices in raw HTML | What can go wrong |
|---|---|---|---|
| Proton VPN | 200 | yes, each amount once | currency is tied to location, not Accept-Language
|
| Surfshark | 200 | yes, mixed with unrelated amounts | publishing a figure that is not a billed price |
| NordVPN | 403 | no (challenge page) | silently keeping an old price without its date |
- A 200 is not a reading. Surfshark answered 200 with more amounts than there are plans. The check that matters is "does this amount sit next to its billing sentence".
- A missing reading must stay visible. The tempting failure is the quiet one: the script fails, the old price stays, the "updated" date moves. A price that could not be read is marked as such.
-
Count occurrences. "Each billed amount appears exactly once" is a cheap invariant. The day Proton's page shows
$59.76three times, the layout changed and the parser needs a human. - Write down where you read from. Location changes the currency, so the reading is only reproducible with it.
The page these readings feed, with every price dated, is here: Black Friday VPN 2026: deals, dated price readings and the fake-deal traps. Disclosure: that page contains affiliate links, this post does not.
If you monitor prices on pages like these, how do you handle the challenge-page case? I would rather show an old dated price than a fresh wrong one, but I am curious what others do.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.