Overview
Something stopped working and Netflix did not tell you what. Perhaps the catalogue went thin overnight — no error, no message, just a home screen with nothing on it but Netflix's own shows. Perhaps a device you have used for years is suddenly not part of your Netflix Household. Or perhaps the SmartDNS you paid for has never worked with Netflix at all, however carefully you followed the setup.
All three come back to the same question — what Netflix reads when you connect — and to a distinction almost every guide on this subject gets wrong. Netflix runs two separate enforcement systems. One decides whether your device belongs to your household. The other decides whether your IP address is an anonymiser. They ask different questions, they respond to different fixes, and the advice repeated everywhere — "pick one server and stay on it" — is aimed at the first while most people are being blocked by the second.
The SmartDNS case is the clearest way in, because it is the one with a definite answer: it cannot work with Netflix, has not since early 2016, and no change of provider will alter that. Why it fails tells you exactly what Netflix is looking at — which is what the rest of this page builds on.
This page is about the mechanism, not about a product. If you already know why and just want the practical route, the Netflix setup guide and library comparison covers how to configure it and what is actually in each country's catalogue.
Key Takeaways
- SmartDNS cannot work with Netflix — it redirects DNS lookups and never changes your IP, which is the only thing Netflix reads
- Netflix runs two separate systems: Household asks whether a device is on your home connection, the proxy block asks whether the address is an anonymiser
- Household keys on IP stability. The proxy block keys on IP reputation. Fixing one does nothing for the other
- A router VPN gives every device one consistent IP — and is rejected anyway, because a datacenter address is still a datacenter address
- The modern block is usually silent: no error screen, just a catalogue containing nothing but Netflix Originals
What is evidenced here, and what is not
Netflix's own statements are quoted as such — the Household criteria, the terms of use, the 2016 proxy-detection announcement. Where something is a forum report or a third-party test, it says so and names the source.
Netflix does not publish its detection stack. So this page says what is well-evidenced — that Netflix keys on IP reputation — and does not name a vendor as its supplier, because nobody outside Netflix can. Where a figure comes from a detection company's own marketing, it is attributed to that company rather than presented as an independent measurement.
Everything volatile is date-stamped. Every claim here was checked 27 August 2026. Enforcement in this space changes on a scale of weeks, which is exactly why there is no list of VPNs that work right now anywhere on this page.
Why SmartDNS can't work with Netflix
Start with what SmartDNS actually does, because the name is doing a lot of work. It replaces the DNS resolver your device uses, and when you look up a domain that a streaming service uses for geo-detection, it points you at a proxy in the target country instead of the real address. Everything else — the video itself, and every other site you visit — goes out over your normal connection, from your normal address.
That is not a criticism. It is the design, and the vendors say so in their own documentation. In NordVPN's wording: "You don't get a new IP address — SmartDNS simply changes how a website sees your IP address." Surfshark, Private Internet Access, ExpressVPN and Bitdefender all describe it the same way. Nobody is hiding this.
The whole argument in one line
The trick worked once. Netflix used to lean on DNS-level signals for geo-detection, and redirecting those lookups was enough to move you. It abandoned that approach years ago in favour of reading the address you connect from and checking it against a reputation database. From that moment SmartDNS was structurally dead for Netflix — not blocked, but bypassed. It is answering a question Netflix stopped asking.
SmartDNS endpoints are catalogued in their own right, too. GeoComply's detection product lists "Smart DNS Proxies" as a category alongside VPNs, proxy servers, Tor exit nodes and hosting providers. These are known, named, indexed addresses — not something clever that slips through unnoticed.
| Property | SmartDNS | VPN | Why it matters |
|---|---|---|---|
| Changes the IP the service sees | No | Yes | The decisive row. SmartDNS redirects name lookups; it never carries your traffic, so your own address is what connects. |
| Encrypts your traffic | No | Yes | SmartDNS is not a privacy tool and does not claim to be. It is a routing trick for geo-detection lookups. |
| Full-speed streaming | Yes | Mostly | SmartDNS leaves video traffic on its normal path, so there is no tunnel overhead. This is its genuine advantage. |
| Works on devices with no VPN app | Yes | Only via the router | Smart TVs, consoles and streaming sticks take DNS settings directly. A VPN reaches them only from the router. |
| Gets past Netflix | No | Sometimes | SmartDNS fails structurally. A VPN fails only when that particular address has been flagged — which is a moving target, not a permanent one. |
| Helps with Netflix Household | No | Only from the router, and only partly | Household is judged on the external IP your devices share. SmartDNS does not touch it; a router VPN unifies it but hands over a datacenter address instead. |
January 2016: the month it stopped
There is a date on this. Netflix expanded to 190 countries on 6 January 2016. Eight days later, on 14 January, David Fullagar — then its VP of Content Delivery Architecture — published a post titled Evolving Proxy Detection as a Global Service, announcing that people using proxies and unblockers would shortly be able to reach the service only in the country they were actually in. The blocks rolled out from around 20 January through February. By March, CBC was reporting that UnoTelly, one of the best-known SmartDNS providers of the era, had effectively given up on Netflix.
That is a useful test for any guide you read on this subject. If it still recommends SmartDNS for Netflix, it is running on knowledge from before 2016 — and it is worth wondering what else on the page has not been checked since.
Ten years on, and the recommendation is still in circulation. via GIPHY
SmartDNS is not useless — it is useless for Netflix
Independent testing by VPNMentor found that Smart DNS Proxy "doesn't work with Netflix, but it can access other platforms like Disney+, Hulu, HBO Max, BBC iPlayer, Peacock TV" — which is exactly what the mechanism predicts. Some testing disagrees, notably WizCase, which shares an ownership group with a VPN it recommends. Services less aggressive about IP reputation are still reachable this way, and if what you want is BBC iPlayer on a TV that cannot run a VPN app, SmartDNS remains a reasonable and genuinely fast choice.
Peacock is a good illustration of the difference in strictness between services — our Peacock walkthrough goes through what that service checks and where it is more forgiving than Netflix.
Netflix runs two enforcement systems, not one
Here is the part almost every guide gets wrong, and it is not a small distinction — it is the difference between advice that works and advice that sounds right and fails.
Netflix Household
Asks whether a device is on your home connection. It is looking for stability — an external IP that keeps turning up in the same place, alongside the same devices, on the same account.
The proxy block
Asks whether an address is an anonymiser. It is looking for reputation — who owns the range, and whether it has been catalogued as datacenter, VPN or proxy infrastructure.
Netflix is unusually clear about the first one. Its help pages state that a Netflix Household is "a collection of devices connected to the internet at the main place where you watch Netflix", and that it establishes that household "based on IP address, device IDs, and account activity" — adding, pointedly, that it does not collect GPS data. It also spells out the trigger: if you have multiple Wi-Fi networks it may associate only one with your Household, and a device connecting through a different ISP account or a different external IP may be asked to verify.
About the second one it says almost nothing, which is normal — publishing your detection criteria is publishing the workaround. But the behaviour has been consistent since 2016 and is easy to observe: addresses that belong to hosting and VPN networks get refused, and addresses that belong to ordinary consumer ISPs do not.
| Netflix Household | The proxy block | |
|---|---|---|
| The question it asks | Is this device on your home connection? | Is this address an anonymiser? |
| What it keys on | IP stability, plus device IDs and account activity | IP reputation — datacenter ranges, known VPN and SmartDNS addresses |
| What you see | "This device isn't part of your Netflix Household" | Error M7111-5059, or — more often now — a catalogue of nothing but Netflix Originals |
| What actually fixes it | Being on the real home network, or completing the verification flow | A clean residential IP address |
| Does a stable IP help? | Yes — stability is the entire point | No. A permanently static address is still blocked if its range is not residential |
The consequence nobody draws
Put a VPN on your router and every device in the house — TV, phone, laptop, console — leaves through one address that never changes. On Household's terms that is a textbook home connection: perfectly stable, perfectly consistent, exactly what the system is looking for.
And Netflix rejects it, because the proxy block is a different system asking a different question, and the answer to that question is that the address belongs to a datacenter. You did not fail the stability test. You passed it, and then failed the reputation test standing right behind it.
Consistency is half the answer, and it is the half that doesn't matter
The evidence that reputation beats stability
If you want a single case that separates the two variables cleanly, it comes from a NANOG mailing-list thread in June 2016. The network engineer Owen DeLong described a home IP block — 192.159.10.0/24, static, his own, in place "for many years" — being blocked by Netflix. Not because it moved around. Because, in the wording he was given, it was not from a known residential ISP.
That is as stable as an address gets. It was blocked anyway. Stability was never the variable being measured.
One limit on that case
If the idea that an address is judged by who owns its range rather than by how it behaves sounds strange, it is the same mechanism that makes a self-hosted VPN fail on day one. We took that apart in detail in the self-hosted VPN post : a brand-new cloud instance is classified as datacenter before it has sent a single packet, because the classification attaches to the range and not to you.
What Netflix actually does when it catches you
Most people picture the error screen: "You seem to be using an unblocker or proxy." Code M7111-5059. It still appears, but it is no longer the usual outcome, and the usual outcome is the reason a lot of people never work out what happened to them.
The block that doesn't tell you it's a block
This behaviour has been reported since around 2021 and is still current — What's on Netflix and Windscribe both document it. From Netflix's side it is a sensible design: an error screen is a support ticket and an angry tweet, whereas a quieter catalogue is something most people put down to titles rotating out.
Which is why the useful diagnostic question is not "did I get an error" but "does the catalogue look right". If your home screen is wall-to-wall Netflix productions and the licensed films you were watching last week have gone, you are being blocked. You simply were not told.
| What you see | Which system | What it means | First move |
|---|---|---|---|
| "This device isn't part of your Netflix Household" | Household | Your device connected from an external IP that Netflix does not associate with your home. | Verify the device by email or text, or get it back onto the home Wi-Fi. |
| Error M7111-5059, "you seem to be using an unblocker or proxy" | Proxy block | The address you connected from is on a list of VPN, proxy or datacenter ranges. | Nothing on the device will fix this. The address itself has to change. |
| The catalogue is suddenly thin and everything is a Netflix production | Proxy block | You are being blocked without being told. Netflix is serving only the content it holds worldwide rights to. | Disconnect the VPN and reload. If the catalogue refills, that was the block. |
| A title plays at home but not on mobile data | Neither | Two different countries, two different licensing catalogues. Nothing is blocking you. | Check whether the title is licensed where you currently are. |
| One device in the house is blocked and the rest are fine | Household | That device is reaching the internet through a different external IP — a second router, a guest network, or mobile data. | Put it on the same network as the TV that anchors the Household. |
The fourth row is worth dwelling on, because it is the one people most often misdiagnose as a block. Catalogues genuinely differ by country, so a title that plays at home and not on mobile data may be a licensing difference rather than an enforcement action. Live sport is the extreme version of this, where rights are carved up by territory so finely that a VPN cannot help at all — our guide to watching sport abroad separates the four different kinds of block that get confused with each other there.
Do VPNs still work with Netflix?
Fragile, not dead. That is the honest one-line answer, and the two words are doing different jobs.
The large commercial providers survive by outrunning the blocklist. Netflix flags addresses; the provider retires them and brings fresh ones online; some of the new ones work until they are flagged in turn. Nothing about that cycle is stable, which is why your VPN worked in March and stopped in November without you changing a setting. Nothing on your side changed. The address's status did.
Why any list of working VPNs goes stale
A "VPNs that work with Netflix right now" list describes a system that moves weekly. It is also the most affiliate-saturated claim in the category, and few of the pages making it ever go back and re-test.
The durable version is this: datacenter IP addresses are inherently detectable, and residential ones are not — yet. That will still be true when this month's brand recommendations have expired.
What "detectable" actually means
Addresses are not judged individually. They are grouped into ranges, ranges are registered to organisations, and organisations are classified — consumer ISP, mobile carrier, hosting provider, university, and so on. Commercial databases sell that classification, continuously updated, and any service that wants to refuse anonymisers buys one rather than building it.
For a sense of scale: GeoComply describes its GeoGuard product as a regularly updated database of over 370 million IP addresses, pre-integrated with Akamai and Amazon CloudFront since 2018, and cites testing by Kingsmead Security reporting 99.1% VPN detection with no false positives. Those figures come from GeoComply's own announcement in September 2025, so treat them as a vendor's claim about a vendor's product rather than as an independent benchmark — but even discounted, they tell you what this industry is selling and roughly how well it works.
GeoComply's published customer list names the BBC, ITV, beIN Sports, DAZN and Amazon Prime Video. Netflix is not on it, and Netflix does not disclose which vendor it uses. The evidence supports the behaviour rather than the supplier: Netflix keys on IP reputation, and which company sells it that data is a detail nobody outside Netflix has established.
What Netflix's terms say, and what actually happens
These are two different questions and it is worth keeping them apart, because the gap between them is where most of the scaremongering lives.
The policy
Netflix's Terms of Use restrict viewing to the country where you established your account and state that Netflix will use technologies to verify your geographic location. Separate clauses permit termination or restriction of an account for suspected violation. The permission to act is unambiguous.
The enforcement
There is no documented case of an account being terminated for geo-hopping with a VPN, and no subscriber has faced legal action over it. The observed consequence is being blocked or shown only Originals — an access problem, not an account problem.
Netflix can terminate. It does not appear to. That is not a blessing, and "no documented cases" is a statement about the evidence rather than a guarantee about the future — a company that has reserved the right can start using it. It is your risk to take, and a small one, but worth taking knowingly. The same split runs through the banking and residency side of the same question , where the gap between what the terms permit and what actually happens is much narrower, and the downside is considerably worse than a thin catalogue.
The residential IP question
If the proxy block judges an address by the company it keeps, the structural answer is an address that keeps ordinary company. A residential IP belongs to a consumer ISP's pool, sitting among millions of ordinary customers that Netflix has no interest in refusing. There is nothing to flag, because flagging it would mean flagging the neighbours.
There is a neat piece of indirect evidence for this. In 2022 GeoComply announced what it called industry-first technology for detecting hijacked residential IP addresses. You do not build that unless clean residential addresses were getting through — the detection industry effectively conceding the point by moving on to the next problem.
Mysterium: genuinely different, with three things you need to know first
Mysterium is a decentralised VPN: instead of renting racks in datacenters, it routes traffic through nodes run by individuals on their own residential connections, who opt in and are paid in the network's token for the hours and gigabytes they carry. That is not a marketing distinction, it is a different network topology, and it produces exactly the property this whole page has been describing — traffic that exits from an ordinary consumer address. Independent-leaning testing from How-To Geek, VPNMentor and State of Surveillance reports it getting past Netflix more reliably than conventional VPNs, specifically for that reason.
Not the same thing as a residential proxy network
There are three real costs to this model. None is a dealbreaker on its own, but you should know all three before you sign up:
- The exit node is a stranger. Your traffic leaves through somebody's home connection, and whoever runs that node is in a position to observe anything you send unencrypted. Most of what you do is inside HTTPS, which limits the exposure considerably, but this is a genuinely different trust model from a company with a legal entity and a reputation to lose. Decide whether you are comfortable with it rather than assuming it away.
- The no-logs claim is unaudited. Several conventional providers now commission third-party audits of theirs; Mysterium's has not been independently verified. Unaudited is not the same as untrue — it means nobody outside the company has checked.
- Residential bandwidth is metered, and streaming eats it. Node operators are paid per gigabyte carried, so the cost model passes through to you. Video is the most bandwidth-hungry thing you can do with a VPN, and heavy streaming gets expensive quickly. The per-gigabyte rate moves with token price and network demand, so treat "expensive for heavy viewing" as directional and check what it currently costs before committing.
All three are structural — they follow from what a decentralised exit node is, rather than from anything Mysterium has done. Mysterium has not been implicated in any law-enforcement action. The sharper end of the risk falls on the people running the nodes: Mysterium's own FAQ warns operators in the US, UK, Canada, Italy, Australia, Germany and India that traffic leaving their address is their legal problem. That is a reason to think hard before running a node, more than before using one.
Router-level VPN: what it fixes and what it doesn't
Putting the VPN on the router instead of on each device is the standard advice for Netflix problems, and it is half good. Splitting it along the two systems shows exactly which half.
What it genuinely solves
- Every device in the house leaves through one external address, which is the consistency Household's logic is built around.
- It is the only way to get a VPN onto hardware that cannot run a VPN app at all — smart TVs, Fire Sticks, Chromecasts, most consoles.
- Nothing on any device can leak around it, because there is no other route out.
What it cannot touch
- IP reputation. Moving the tunnel from your laptop to your router does not change whose network the exit address belongs to.
- The proxy block, therefore, applies exactly as before — with the added irony that it now applies to every device at once.
- Router throughput. Encryption is CPU-bound, and a router without hardware crypto acceleration will cap your streaming bitrate well below what the line can do.
The versions of this that people report working are instructive, because they are not really router VPNs in the usual sense. The long-running "VPN Director" thread on SNBForums documents users routing devices back through the account owner's actual home connection — sometimes over a mesh product like NordVPN's Meshnet — so that the traffic emerges from the residential address the Household was established on. That works because the exit is a real home line. Point the same setup at a commercial server in a datacenter and the reputation test is waiting at the other end.
How firm is this?
If you do go the router route, WireGuard on hardware with AES-NI or ARMv8 crypto acceleration is the practical baseline, and split tunnelling lets you exempt traffic that should stay on the normal path — your banking apps, for one, which react badly to datacenter addresses for reasons we went through separately . AsusWRT-Merlin, GL.iNet, DD-WRT and OpenWRT all support it; the setup walkthrough covers the configuration end.
One address for every device, and still the wrong kind of address. via GIPHY
Locked out and you weren't even cheating
Everything above assumes you are trying to reach a catalogue you are not entitled to. A large number of people hitting these messages are doing nothing of the kind — they are paying for one account, using it themselves, and running into a system that assumes a household is a fixed place with one internet connection. Plenty of households are not.
Full-time RV and van dwellers
There is no fixed home Wi-Fi to check in from, and the check-in is the whole mechanism.
One user on the Bogleheads forum described the bind exactly: their home Wi-Fi did not reach far enough to pick up in the RV parked on their own driveway.
People with two homes
Only one connection can be the Household, so the other one is permanently the away address.
Netflix is explicit that where there are multiple Wi-Fi networks it may associate only one with your Household.
Split families and students
One account, one billing address, and people who genuinely live at different addresses.
This is the case the paid-sharing rules were designed to catch, and it catches separated parents and children at university with the same net.
One house, two routers
A second router or a separate ISP line puts some devices on a different external IP.
A same-house couple reported exactly this on JustAnswer — the wife's tablet was blocked while sitting in the same building as the TV.
Netflix has also, according to reports, tested rules strict enough that teachers could not reach their own account from their own classroom. Whether or not that particular case survived, it illustrates the shape of the problem: the rule is a proxy for "do these people live together", and proxies have edges.
Netflix's own remedies, which cost nothing
These are the supported routes. They are not workarounds, they are features, and they are worth trying before you reach for anything technical — a VPN aimed at a Household problem will usually make it worse, since it changes the external IP that Household is trying to recognise.
7 days
Temporary access code
For travel and temporary stays. Netflix issues a code granting seven consecutive days of access on a device outside the household.
31 days
The check-in window
Household devices need to connect to the home Wi-Fi and watch something at least once every 31 days to stay associated. This is the clock that catches people who move around.
15 min
Verification link
The email or text link used to confirm a device expires after fifteen minutes. Have the device in front of you before you send it.
A number worth checking yourself
Verifying a device that isn't in your household
- 1
Settings → Manage Netflix Household
On the account you are trying to watch on, or from the Netflix app on a device already in the household.
- 2
Update Netflix Household
Starts the flow that re-associates devices with your home connection.
- 3
Send Email or Send Text
The link goes to the address or number on the account, not to the device asking.
- 4
Open the link within 15 minutes
It expires. If you miss the window, start again — the flow is repeatable.
- 5
"Yes, This Was Me"
Confirms the device. It stays verified as long as it keeps checking in.
If you have no fixed home connection at all
The honest verdict
SmartDNS and Netflix is a closed question. It does not work, it cannot be made to work, and no provider will ever fix it, because the thing it does not do is the only thing Netflix looks at. If you are paying for SmartDNS for Netflix, stop. If you are paying for it for BBC iPlayer on a smart TV, carry on — that is a different service with different criteria and SmartDNS is a good fit for it.
A VPN is fragile rather than dead. It works when the address you were handed has not been flagged yet, and stops when it has. That is not something you can configure your way out of, and it is why this page has no list of providers that work today — such a list describes a system that will have moved before you finish reading it.
Household and the proxy block are separate, and this is the part to keep. One wants a stable address; the other wants a reputable one. Advice that fixes stability — one server, never switch, put it on the router — leaves reputation untouched, which is usually the thing refusing you. Diagnose which message you are actually getting before you spend money on either.
Residential exit addresses are the only structural answer to a reputation test, which is why Mysterium is the one genuinely differentiated recommendation on this page — and why it comes with a stranger operating your exit node, an unaudited no-logs claim and metered bandwidth attached. Every conventional VPN, however good its apps or its extra features, hands you a datacenter address — and that is the thing being screened.
And if you are being blocked in your own home, the answer is not technical at all. It is the verification flow, the seven-day code and the 31-day check-in — free, supported, and worth exhausting before you buy anything.
Shelf life of this page
References
- [1]Evolving Proxy Detection as a Global Service — Netflix (David Fullagar, VP of Content Delivery Architecture), 2016. https://about.netflix.com/en/news/evolving-proxy-detection-as-a-global-service
- [2]
- [3]Netflix says, "Your TV/device isn't part of the Netflix Household" — Netflix Help Center, 2026. https://help.netflix.com/en/node/127200
- [4]
- [5]
- [6]911 S5 Botnet Dismantled and Its Administrator Arrested in Coordinated International Operation — US Department of Justice, 2024. https://www.justice.gov/archives/opa/pr/911-s5-botnet-dismantled-and-its-administrator-arrested-coordinated-international-operation
- [7]GeoIP Anonymous IP database — how anonymiser addresses are classified — MaxMind, 2026. https://www.maxmind.com/en/geoip2-anonymous-ip-database
All claims verified 27 August 2026. Some sources are attributed inline rather than linked — the June 2016 NANOG thread, the VPNMentor and WizCase SmartDNS results, the SNBForums router thread, and the Bogleheads and JustAnswer household reports — because we could not confirm a stable canonical URL for each and would rather name the source than guess a link. Netflix does not publish its detection stack, so no detection vendor is named as its supplier anywhere on this page.
SmartDNS, VPNs and Netflix Household FAQ
Does SmartDNS work with Netflix?
Why does Netflix only show Originals when I use a VPN?
What is Netflix Household and does a VPN trigger it?
Will using one VPN server consistently avoid Netflix blocks?
Does a router-level VPN fix Netflix Household problems?
Can Netflix ban my account for using a VPN?
Why did my VPN stop working with Netflix?
What's the difference between SmartDNS and a VPN?
I'm not sharing my account, so why does Netflix say my device isn't in my household?
Is a residential IP the same thing as a residential proxy?
Does Netflix use GeoComply's GeoGuard?
Should I just cancel and use a local service instead?
Netflix's enforcement moves quickly, so confirm anything time-sensitive in these answers before you rely on it.
