Denied Access

Issue abstract: I continue to get blocked from websites or searches when using my VPN. I change location and it still happens. I’ve also been getting blocked from websites with a message from Cloudfare.

Detailed description: On a newspaper website today, I used the search feature while in DuckDuckGo. I got this error. Then I tried the same in Edge InPrivate. Same error. I changed the VPN location. Same error.

Too Many Requests
client_ip: 15.181.49.66
request_id: 7031471543

Are there security issues with the VPN IP addresses that Norton is using? What’s going on? I thought using Norton VPN would keep my computer and information secure and private AND allow me to access websites and content on the Internet. This is very frustrating.

Product & version number: Norton 360 / 26.3.10886 (build 26.3.10886.979)

OS details: Windows 11 Pro

What is the error message you are seeing?

Too Many Requests
client_ip: 15.181.49.66
request_id: 7031471543

If you have any supporting screenshots, please add them:

Hello @ChangeAlchemist
Please try running Norton LiveUpdate + Restart (not Shut down) machine

Norton Security 26.4.10932 for Windows is now available!

==============================================

Hello @ChangeAlchemist

fwiw ~ ChatGPT (Norton app)

What you’re seeing is very common with VPNs, and it’s not really a “Norton is broken” situation—it’s more about how modern websites defend themselves.

Here’s what’s actually going on behind the scenes.


:prohibited: Why Cloudflare is blocking you

Services like Cloudflare sit in front of millions of websites and aggressively filter traffic to stop bots, scraping, and attacks.

When you use a VPN (including Norton’s), you’re sharing an IP address with lots of other users. That creates a few problems:

1) Bad IP reputation (big one)

  • VPN IPs are reused by thousands of people.
  • If even a fraction of those users do scraping, spam, or abuse → that IP gets flagged.
  • Cloudflare uses reputation databases and may block or challenge that IP automatically. ([SEO North][1])

:backhand_index_pointing_right: This is the #1 reason you’re getting blocked.


2) “Too Many Requests” = rate limiting

Your error:

Too Many Requests

This usually means:

  • That shared VPN IP made too many requests in a short time
  • Could be from other users on the same VPN server, not you

Cloudflare treats it like a possible bot/DDoS pattern and temporarily blocks it. ([SEO North][1])


3) VPNs look like proxies (higher suspicion)

Cloudflare explicitly scores traffic for “bot-like” behavior:

  • Datacenter IP (VPN) :cross_mark:
  • Many users behind one IP :cross_mark:
  • Rapid requests :cross_mark:

Even legit users get caught because of this scoring system. ([SentraCell][2])


4) Site owner settings (not Norton)

Important point:

  • Cloudflare doesn’t decide alone—the website owner sets the strictness.
  • Some sites (news, search pages) use aggressive filtering.

So:

Same error in DuckDuckGo + Edge = expected
Because the block is IP-based, not browser-based.


5) Changing VPN location doesn’t always help

You tried switching locations—but:

  • Many VPN providers recycle the same IP pools
  • New location ≠ new clean IP
  • You may just land on another flagged IP

:locked: Is Norton VPN “unsafe” or compromised?

No—this isn’t a security failure.

Your VPN is still:

  • Encrypting your traffic
  • Hiding your real IP

But:

Privacy ≠ guaranteed access

Modern websites increasingly block VPN traffic by design.


:warning: Why this is getting worse (industry trend)

  • Anti-bot systems are stricter than ever
  • VPN IP ranges are widely known
  • Some regions/services even intentionally block VPN traffic (legal or anti-abuse reasons)

Even big VPNs like Nord, Proton, etc. have the same issue.


:brain: What your specific error tells me

This line:

client_ip: 15.181.49.66

That’s likely:

  • A cloud/datacenter IP range
  • Not residential → higher chance of being flagged

:white_check_mark: What actually helps (practical fixes)

Try these in order (these are the ones that actually work in real-world use):

1) Turn VPN OFF (quick test)

  • If the site works instantly → confirms IP reputation issue

2) Switch servers multiple times

  • Don’t just change country—cycle several servers
  • You’re looking for a “clean” IP

3) Wait 10–30 minutes

  • Rate limits often expire quickly

4) Use a different network (mobile hotspot)

  • Gets you a fresh ISP IP
  • Good way to confirm it’s not your device

5) Use VPN only when needed

  • Example:

    • Off for browsing/search
    • On for privacy-sensitive tasks

:compass: Straight answer to your main question

“Are there security issues with Norton VPN IP addresses?”

Not exactly. The issue is:

:backhand_index_pointing_right: Norton VPN uses shared datacenter IPs that often have poor reputation,
and Cloudflare aggressively blocks those.


:speech_balloon: Bottom line

  • Nothing is wrong with your PC or browser
  • Nothing is “hacked” or compromised
  • You’re running into modern anti-bot + anti-VPN defenses

=============================================

What your setup likely looks like
With Norton 360 v26.x on Windows 11:

  • Norton Secure VPN = ON (system-wide)
  • All browsers (Edge, DuckDuckGo, etc.) → routed through VPN
  • Websites see a shared VPN IP (like 15.181.49.66)

:backhand_index_pointing_right: That’s why:

  • Same error across different browsers
  • Changing browser doesn’t fix it
  • Only changing VPN behavior matters

:prohibited: Why you’re getting “Too Many Requests”

That specific error means:

  • The VPN IP you’re using has:
    • Too many requests (from many users)
    • Or a bad reputation score
  • Cloudflare rate-limited or blocked it

This is extremely common with:

  • Shared VPN IP pools
  • Datacenter-based VPNs (like Norton’s)

:magnifying_glass_tilted_left: What Norton isn’t telling you clearly

Norton Secure VPN:

  • Uses shared IP addresses
  • Does not give you a unique residential IP
  • Rotates IPs, but from the same general pool

So even if you:

  • Change location
  • Reconnect

:backhand_index_pointing_right: You often land on another flagged IP


:test_tube: Confirm it in 10 seconds

Do this:

  1. Open Norton 360
  2. Turn Secure VPN OFF
  3. Reload the blocked site

If it works immediately:
:backhand_index_pointing_right: That confirms 100% the issue is VPN IP reputation


:warning: Important reality check

“I thought VPN = secure + private + full access”

That used to be closer to true. Now:

  • VPN = privacy + encryption
  • But :cross_mark: NOT guaranteed access

Many sites now:

  • Detect VPNs instantly
  • Block or throttle them

:white_check_mark: Practical ways to deal with it

Here’s what actually works in real life:

Option 1: Use VPN selectively (best balance)

  • OFF → normal browsing/search
  • ON → when you want privacy (Wi-Fi, sensitive activity)

Option 2: Keep switching servers

  • Sometimes you’ll hit a “clean” IP
  • Not reliable, but works occasionally

Option 3: Use split behavior (manual)

Since Norton doesn’t support true split tunneling well:

  • Use:
    • One browser with VPN OFF (main use)
    • Turn VPN ON only when needed

Option 4: Accept the trade-off

  • Privacy ↑
  • Accessibility ↓

That’s just how modern anti-bot systems work now.


:speech_balloon: Bottom line for your exact case

  • Your Norton 360 version is fine
  • Your system is not compromised
  • The issue is:

:backhand_index_pointing_right: Shared Norton VPN IPs getting flagged by Cloudflare rate limits

=============================================

DuckDuckGo or InPrivate mode are not the cause of the blocks.
But they can slightly increase the chances of being flagged when combined with a VPN.

Let’s break it down clearly.


:brain: What actually matters most

The dominant factor in your case is still:

:backhand_index_pointing_right: Your VPN IP (from Norton Secure VPN)

That’s what Cloudflare is reacting to.

Everything else (browser, search engine, private mode) is secondary.


:magnifying_glass_tilted_left: What DuckDuckGo does (and doesn’t do)

DuckDuckGo:

  • Doesn’t track you
  • Doesn’t personalize results
  • Doesn’t store identifying cookies

But importantly:

  • It does NOT hide your IP
  • It does NOT act like a VPN

So by itself:
:backhand_index_pointing_right: It does not cause blocks


:detective: What InPrivate mode (Edge) changes

Microsoft Edge InPrivate mode:

  • Clears cookies/session after you close it
  • Reduces stored tracking data

But during a session:

  • Your IP is still visible (VPN IP in your case)
  • You may have fewer cookies / less “history”

:warning: Why private modes can increase blocking slightly

This is the subtle part:

When you combine:

  • VPN IP (already suspicious) :cross_mark:
  • No cookies / fresh session :cross_mark:
  • No browsing history :cross_mark:

Cloudflare sees:

“Unknown user + high-risk IP”

That can:

  • Lower your “trust score”
  • Trigger stricter rate limits or blocks

:counterclockwise_arrows_button: Why you saw the same error everywhere

You tested:

  • DuckDuckGo :check_mark:
  • Edge InPrivate :check_mark:
  • Different VPN locations :check_mark:

Same result → that tells us:

:backhand_index_pointing_right: The block is IP-based, not browser-based


:test_tube: Real-world comparison

Setup Likelihood of being blocked
Normal browser, no VPN Low
VPN only Medium–High
VPN + InPrivate High
VPN + InPrivate + privacy search Slightly higher

But again:

The VPN is doing ~90% of the triggering


:compass: What to do (based on your setup)

If a site is blocking you:

  • First try: turn VPN off
  • If you want privacy:
    • Use DuckDuckGo OR InPrivate
    • But keep VPN off for that site

That usually works better than stacking everything at once.


:speech_balloon: Bottom line

  • DuckDuckGo :cross_mark: not the problem
  • InPrivate :cross_mark: not the problem
  • VPN :white_check_mark: main cause

But:

Combining all three makes you look more anonymous—which ironically makes you look more like a bot to systems like Cloudflare.

=============================================

Using all three together—Norton Secure VPN + Microsoft Edge InPrivate + DuckDuckGo—removes most of the normal signals websites use to recognize a “trusted” human visitor.

So instead of seeing:

a consistent user with history and normal behavior

they see:

a shared, high-risk IP + no history + no identifiers

That combination looks like:

  • Many users behind one IP (VPN)
  • No cookies or session continuity (InPrivate)
  • No tracking/profile data (DuckDuckGo)

:backhand_index_pointing_right: Which closely matches how automated bots behave.

In one line:

You appear as an anonymous, constantly-reset user coming from a crowded IP—a pattern that anti-bot systems often treat as suspicious.

=============================================

If you want fewer blocks without giving up all privacy, the trick is to stop stacking every anonymity layer at once and use them more strategically.


:compass: Practical setup that works

:white_check_mark: 1) Make VPN “on-demand,” not always-on

With Norton Secure VPN:

  • OFF → everyday browsing, search, news sites
  • ON → public Wi-Fi, sensitive activity, logins you want extra privacy for

:backhand_index_pointing_right: This alone will eliminate most Cloudflare blocks.


:white_check_mark: 2) Don’t stack all 3 at once unless you need to

Instead of:

VPN + InPrivate + DuckDuckGo (high block risk)

Use combos like:

  • Normal browser + DuckDuckGo → good privacy, low blocking
  • VPN + normal browser (not InPrivate) → better success rate
  • InPrivate only (no VPN) → still private enough for many cases

:white_check_mark: 3) Keep some “trust signals”

Sites trust you more when they see:

  • Stable session (cookies not constantly wiped)
  • Normal browsing patterns
  • Non-shared IP

So:

  • Avoid using InPrivate for every visit
  • Let trusted sites (news, shopping) run in a normal session

:white_check_mark: 4) If blocked, don’t fight it—switch approach

When you hit a block:

  1. Turn VPN off → retry
  2. Or switch VPN server a few times
  3. Or wait 10–15 minutes (rate limit resets)

:white_check_mark: 5) Use two-browser strategy (very effective)

Example:

  • Browser A (Edge normal)

    • VPN OFF
    • For everyday sites
  • Browser B (or Norton Private Browser)

    • VPN ON
    • For privacy-focused sessions

:backhand_index_pointing_right: This avoids constant toggling.


:warning: What NOT to expect anymore

Even with perfect setup:

  • Some sites will still block VPNs entirely
  • This is now intentional behavior, not a bug

:speech_balloon: Bottom line

To reduce blocks:

Use fewer layers at once, and turn VPN on only when you actually need it.

That gives you:

  • 80–90% of the privacy
  • Way fewer “Too Many Requests” errors

AI sourced content may make mistakes

1 Like

fwiw ~ ChatGPT (Norton app)

Summary

:receipt: What’s causing the “Too Many Requests / Cloudflare” blocks

This is not a problem with your PC or browser, and not a security breach.

The main cause is:

Shared VPN IP addresses used by Norton Secure VPN

When the VPN is ON:

  • You share an IP with many other users
  • If that IP sends a lot of traffic (from anyone), it gets rate-limited or flagged
  • Services like Cloudflare may block it with errors like:
    • “Too Many Requests”
    • CAPTCHA challenges
    • Access denied

:magnifying_glass_tilted_left: Why it happens across all browsers

If the user sees the same issue in:

  • Different browsers (Edge, Chrome, DuckDuckGo, etc.)
  • InPrivate / Incognito mode

:backhand_index_pointing_right: That confirms it’s IP-based, not browser-related.


:warning: Why privacy features can make it worse

Using all of these together:

  • VPN
  • Private browsing (InPrivate/Incognito)
  • Privacy search (DuckDuckGo)

Removes normal “trust signals” like:

  • Cookies
  • Session history
  • Unique IP

So websites may treat the user like:

an anonymous, high-risk visitor (similar to bot traffic)


:white_check_mark: Recommended workaround (what actually works)

  1. Turn OFF VPN for normal browsing/search
  • Especially for news sites, search, shopping, etc.
  1. Turn VPN ON only when needed
  • Public Wi-Fi
  • Privacy-sensitive activity
  1. If blocked while using VPN
  • Turn VPN off and retry → should work immediately
  • Or switch VPN server (may or may not help)
  1. Avoid stacking all privacy layers at once
  • VPN + InPrivate + DuckDuckGo = highest chance of blocking

:speech_balloon: Bottom line

  • Norton Secure VPN is working correctly
  • The issue is VPN IP reputation + modern anti-bot systems (like Cloudflare)
  • This behavior is common across all VPN providers, not just Norton

AI sourced content may make mistakes

Hello @ChangeAlchemist
Care to share your progress