
By Lance Allison, Founder of Ruby Digital Agency | October 2026 | ~24 min read
At the end of September we moved The Banksy Shop, a UK shop that has printed Banksy-inspired art and apparel since 2006, from BigCommerce to Shopify. It was a clean cutover: every product, every customer and nearly 19,000 orders came across, the redirects were in place, and the first Shopify orders arrived that same evening. The next morning the owners sent me a screenshot from a phone. Their own website would not open. Chrome said: “This site can’t provide a secure connection. www.thebanksyshop.co.uk sent an invalid response.”
Every check we ran said the site was fine. It loaded from our office in Utah, from a server in London and from every DNS service we tried. Orders kept coming in from the United States, France, the Netherlands and Ireland. And yet the owners could not reach it on mobile data, on public Wi-Fi, or on any of the networks they tried over several days. Every obvious explanation, from DNS propagation to a browser cache to the owners’ own broadband, turned out to be wrong. The real cause was one I had never seen in more than a hundred migrations, and it was quietly costing the shop about half of its UK sales.
The short version: the UK’s mobile networks switch an 18+ content filter on by default, and after the move to Shopify those filters started treating a shop that sells Banksy-inspired T-shirts and canvas prints as adult content. Because the site runs over HTTPS, the block never showed a “this site is blocked” page. It showed a certificate error that looks exactly like a broken SSL setup. We proved it with the Open Rights Group’s free testing tool and a control store, then asked each network to reclassify the site under the BBFC’s framework. O2 cleared it within a working day, and Three the day after we sent it fresh evidence. This case study tells the whole story, with the evidence, the timeline and the check we now run after every UK go-live.
For anyone arriving from a search: “this site can’t provide a secure connection” is the message Chrome, Edge and Samsung Internet show when the secure (TLS) handshake with a website fails, usually with the code ERR_SSL_PROTOCOL_ERROR and the words “sent an invalid response”. Most of the time the cause is a certificate problem on the website, a wrong clock on the device, or security software in the way. In the UK there is a fourth cause that almost nobody checks: a mobile or broadband content filter blocking the site, which surfaces as exactly the same error because the filter cannot present a valid certificate for the page it blocked.
In This Article
- The Client: Nineteen Years of Banksy-Inspired Prints, Now on Shopify
- Go-Live Week: This Site Can’t Provide a Secure Connection
- Every Obvious Explanation Was Wrong
- The Clue Was in Who Was Ordering
- The Real Cause: UK Mobile Networks’ 18+ Filters
- Proving It: blocked.org.uk and a Control Store
- The Fix: Reclassification Under the BBFC Framework
- After the Fix: UK Orders Back to Normal
- Why a Platform Move Can Trigger a Reclassification
- A Quick Overview of Ruby Digital Agency
- A Seven-Step Filter Check for Any UK Store Launch
- What Happens If You Do Nothing
- Frequently Asked Questions
- Final Thoughts
Key Takeaways
- On a UK phone, “this site can’t provide a secure connection” can mean a network content filter is blocking the site, not that the site’s SSL is broken.
- UK mobile networks switch an 18+ filter on by default under the BBFC’s Mobile Classification Framework, and an adult has to pass a credit-card age check to lift it.
- After The Banksy Shop moved from BigCommerce to Shopify, Three and O2 blocked it as 18+ while every server-side check passed and overseas orders carried on.
- The Open Rights Group’s blocked.org.uk proved it in minutes: Three and O2 returned their 18+ pages for the shop, and a control Shopify store on the same servers passed.
- O2 cleared the site about a working day after our request, and Three a day after we sent it fresh evidence; UK orders recovered from about one a day to more than two.
- Any UK store that changes platform should test its domain on blocked.org.uk before and after the DNS switch, because no hosting dashboard, uptime monitor or SSL checker will show this.
The Client: Nineteen Years of Banksy-Inspired Prints, Now on Shopify
If you have ever wanted Banksy’s Flower Thrower on your wall without spending a house deposit, The Banksy Shop is where to look. Since 2006 this independent UK shop has printed Banksy-inspired T-shirts, hoodies, mugs and gallery-grade canvases to order: 354 designs across 172 artworks, shipped to more than sixty countries. The T-shirts start at £14.95, the canvas prints come in six sizes up to 48″×32″ and arrive ready to hang, and UK delivery is free over £30. If you only look at one page, make it the bestsellers, ranked on thousands of real orders.
What I like most about the shop is that it takes Banksy at his word. His work was never meant to sit behind glass, so the shop puts it on things people actually use, prints each piece only after it is ordered, and is refreshingly straight about what it is: a fan-run shop selling Banksy-inspired designs, not affiliated with Banksy or Pest Control. Nineteen years in, plenty of the people ordering today first ordered a decade ago. That kind of loyalty is exactly what you do not want to put at risk when you change platform.
The range is organised around artworks rather than products, which is what nineteen years of listening to customers produces. The same Flower Thrower, Balloon Girl or Pulp Fiction comes as a T-shirt, a ladies’ fit, a hoodie, an embroidered piece, a mug, a cushion or a canvas, and the shop’s About page tells the rest of the story better than I can.
The move itself was a full migration from BigCommerce, done in-house. We brought across every product and variant with its prices, colours and images, around 16,700 customer accounts and nearly 19,000 orders with their original order numbers and tracking, and built a redirect for every old product and category URL. We kept the shop’s Google Shopping history by matching the old product IDs exactly, a subject we cover in our Google Shopping feed migration guide. The storefront was rebuilt on Shopify’s Horizon theme, with print-on-demand fulfilment for the apparel and mugs. If you want the general shape of a move like this, our BigCommerce to Shopify migration guide covers it step by step.
| What moved | Detail |
|---|---|
| Products | 354 live designs across 172 artworks, with every colour, size and frame option |
| Customers | Around 16,700 accounts |
| Orders | Nearly 19,000, with original order numbers and tracking |
| URLs | A 301 redirect for every old product and category page |
| Google Shopping | Same product IDs as the old feed, so the history carried over |
| Go-live | Wednesday 23 September 2026, early evening UK time |
None of that is the reason for this article. The reason is what happened in the six days after the switch.
Go-Live Week: This Site Can’t Provide a Secure Connection
The DNS change went in at about six in the evening UK time on Wednesday 23 September. Shopify issued the security certificates for both thebanksyshop.co.uk and www.thebanksyshop.co.uk about two hours later, and the first Shopify order came in that night. By any normal measure the launch had gone well.
On Thursday morning the owners reported that the site had “crashed”. Their phone showed the Chrome error page with the message “sent an invalid response”. We checked, it loaded for us, and we treated it as the usual go-live noise: a phone still holding the old address while the internet catches up. On Saturday they wrote again. Clicking the Home link or the logo still gave the same error, on mobile and on a laptop. We moved the shop’s primary domain from the www address to the bare domain, partly to force a fresh lookup, and asked them to give it time.
By Sunday afternoon the owners had cleared their caches and were still locked out. More usefully, they had tested far more widely than we had. They had tried mobile data, several different Wi-Fi networks and more than one phone, and they sent three screenshots: Chrome inside the Google app, a full Chrome window and Samsung Internet, all on 4G, all saying the same thing. One line in their message reframed the whole problem for me: it did not matter which network they connected to, they still got the error.
| When (UK time) | What happened |
|---|---|
| Wed 23 Sep, ~6 pm | DNS switched to Shopify; certificates issued about two hours later; first Shopify order that night |
| Thu 24 Sep | Owners report the site has crashed on a phone: “sent an invalid response” |
| Sat 26 Sep | Same error from the Home link and logo, on mobile and a laptop; treated as caching |
| Sun 27 Sep, ~5–6 pm | Still failing after clearing caches, on mobile data and every Wi-Fi tried |
| Sun 27 Sep, ~7 pm | Cause found and proven with blocked.org.uk and a control store |
| Sun 27 Sep, ~8 pm | Reclassification requests sent to every UK mobile network |
| Mon 28 Sep | O2 clears the site |
| Tue 29 Sep | Three clears the site |
That is the sequence I want other store owners to recognise, because it is the sequence that wastes days. A secure-connection error straight after a domain move looks like the most ordinary launch problem there is. The instinct, ours included, is to wait it out.
Every Obvious Explanation Was Wrong
When the owners’ Sunday message arrived, we stopped assuming and went through every cause that can produce this error, one at a time, from outside their network. The point of the exercise was to find something that was broken. Nothing was.
| Suspect | What we checked | Result |
|---|---|---|
| DNS propagation | Answers from Google, Cloudflare, Quad9, OpenDNS and the domain’s own nameservers | All correct |
| A stale address on the phone | Requests sent to the old BigCommerce IP address | It now serves the Shopify shop too, so a stale address cannot produce an error |
| The SSL certificate | Certificates and chain for the bare domain and www | Valid, issued by Let’s Encrypt, renewing automatically |
| Protocol support | TLS 1.2 and 1.3, HTTP/2, HTTP/3, IPv4 and IPv6 | All working |
| Family and security DNS filters | Cloudflare for Families, AdGuard, CleanBrowsing, OpenDNS FamilyShield and others | None blocked the domain |
| Reputation | Google Safe Browsing and VirusTotal | Clean |
| The UK in general | A test server in London | Loaded normally |
Two of those results are worth a sentence each. The stale-address theory, which is what “give it time” really means, was ruled out by an accident of infrastructure. Both BigCommerce and Shopify sit behind Cloudflare, which routes by the name you ask for rather than the address you connect to, so even a phone still holding BigCommerce’s old address was handed the new Shopify site. And the certificate was not merely valid. It used exactly the same chain as many other Shopify stores, including the UK sites of some very large fashion brands, which load on every phone in the country.
The second obvious explanation, that the owners’ home broadband had a filter switched on, was the one we had suggested an hour earlier. It fell apart the moment they told us the error followed them onto mobile data and onto other people’s Wi-Fi. A filter on a home router does not follow you onto someone else’s network. Something was blocking this one domain on every connection the owners used, and on none of the connections we used.
If you are troubleshooting this error on your own store, Cloudflare’s ERR_SSL_PROTOCOL_ERROR guide is a good list of the usual suspects: certificates that have not finished issuing, cipher and protocol mismatches, networks that mishandle HTTP/3, and security software or corporate proxies that inspect encrypted traffic. Its last category is the one that mattered here: parental controls and network-level filtering. Most people skip that line because it sounds like a problem for the visitor rather than the store. In the UK it can be a problem for a large share of your customers at once.
The Clue Was in Who Was Ordering
The breakthrough did not come from a network tool. It came from the orders. Shopify records the browser and the IP address of every online order, so we looked at who had managed to buy something since the switch, and from where.
Orders were arriving at a normal overall rate, roughly four a day, but the mix had changed sharply. On BigCommerce, between July and the switch, 64% of the shop’s orders came from the UK and about 5% from the United States. In the first days on Shopify the United States had jumped to the largest share and the UK had fallen to a quarter. The UK was running at about one order a day against a long-run average of 2.2.
Then we looked up the network behind each UK order, using only the network block rather than the customer’s own address. Every UK order placed in the first four days had come over home broadband: two on BT and two on Virgin Media. Not one had come over a mobile network. For a shop whose customers, like most shops’ customers, buy on their phones, that is not a coincidence.
| Before the switch (BigCommerce) | First six days on Shopify | |
|---|---|---|
| UK share of orders | 64% | About a quarter to a third |
| UK orders per day | 2.2 | About 1 |
| UK orders over a mobile network | Normal mix | None on Three or O2 |
| Orders from other countries | Normal | Normal, US unusually high |
Put that next to the owners’ screenshots and the picture was clear enough to test. Overseas visitors could reach the shop. UK visitors on home broadband, where adults have usually switched filters off or never had them, could reach it. UK visitors on mobile data could not. Whatever was blocking the site was British, network-level and on by default.
The Real Cause: UK Mobile Networks’ 18+ Filters
Every UK mobile network filters age-restricted content by default. The arrangement dates back to July 2013, when the networks appointed the BBFC to provide “the classification framework they use to self-regulate” what can be reached over mobile internet. The BBFC sets the standard for what counts as adult. The networks, or the companies that classify the web on their behalf, decide which sites fall into it.
The filter is on until an adult proves their age. Three’s help page says that all new Three devices have age-restricted content blocked by default and that the account holder can lift it with a credit card in the Three app or with photo ID in a store; debit cards do not count. EE’s Content Lock works the same way, set to Moderate by default and lifted with a credit-card age check, and O2 and Vodafone run equivalent checks. Plenty of adults never bother, and a company phone often cannot be changed by the person using it at all.
| Network | Filter on by default? | How an adult lifts it |
|---|---|---|
| Three | Yes, on all new devices | Credit card in the Three app, or photo ID in store |
| EE (and BT Mobile) | Yes, Content Lock set to Moderate | Credit-card age check in the EE app or by phone |
| O2 | Yes | Credit-card age verification online |
| Vodafone | Yes | Age verification with Vodafone |
The part that makes this so hard to spot is how the block looks. On an ordinary unencrypted page a filter can swap in its own “this site is blocked” notice. On an HTTPS page it cannot, because it does not hold a certificate for your domain. So the phone tries to open a secure connection to your shop, the filter steps in, and the browser reports that the site “sent an invalid response”. The Open Rights Group’s own FAQ describes exactly this: an HTTPS site blocked by a parental-control system is recorded as an SSL error rather than as a definitive block, because the filter’s block page cannot present a valid certificate for the address requested.
In other words, the customer sees the error message from the first paragraph of this article, concludes your shop is broken or unsafe, and leaves. Nobody tells you. Your hosting dashboard, your uptime monitor and your SSL checker all report a healthy site, because from where they sit it is one. And the owners’ run of failed Wi-Fi networks makes sense too: public Wi-Fi in the UK is commonly filtered under the Friendly WiFi scheme, and many home broadband packages switch on a family filter for new customers. Other UK businesses have hit the same wall on broadband; this Sky Community thread follows a company whose valid-certificate site was blocked for Sky customers until it was reclassified.
Proving It: blocked.org.uk and a Control Store
A good theory is not evidence, and I did not want to ask four mobile networks to reclassify a site on a hunch. The tool that settled it is blocked.org.uk, run by the Open Rights Group. It keeps test probes on real UK consumer connections with the networks’ default filters switched on, and anyone can submit a URL. Results come back in seconds and stay public. Before submitting anything, check its probe status page: on the day we tested, only the O2 and Three probes were online, so those were the two networks we could test directly.
We ran four tests on Sunday evening. The first two used the shop’s secure addresses, with and without www, and both came back as an SSL error on Three and on O2, which matched the owners’ screenshots but did not yet prove a block. The third was the important one: the plain http:// address. Over an unencrypted connection a filter can show its own page, and that is exactly what happened. Both networks returned their 18+ block pages, Three’s pointing to its adult-content help page and O2’s to its 18+ access page, and the public result listed both under “ISPs currently blocking this site”.
The fourth test was a control. We submitted another Shopify store, the UK site of a large international fashion brand, served from the same Shopify servers with the same certificate chain, at the same time. It passed on both networks. That one result ruled out every remaining doubt about the probes, the platform and the certificates: the block was specific to thebanksyshop.co.uk.
| Address tested (27 September) | Three | O2 |
|---|---|---|
| https://www.thebanksyshop.co.uk/ | SSL error | SSL error |
| https://thebanksyshop.co.uk/ | SSL error | SSL error |
| http://www.thebanksyshop.co.uk/ | Blocked, 18+ page | Blocked, 18+ page |
| Control: a large fashion brand’s UK Shopify site, same servers and certificate chain | OK | OK |
The same tool held one more useful piece of history. The shop’s address had last been tested in 2017, while it was on BigCommerce, and at that time it passed on every UK network the Open Rights Group monitored: Vodafone, Three, O2, EE, BT, Sky, TalkTalk, Virgin Media and Plusnet. Whatever had changed, it had changed recently.
I want to be precise about what that evening did and did not prove. It proved that Three and O2 were blocking the shop as 18+ and that nothing on our side was at fault. It did not tell us whether EE or Vodafone were blocking it, because their probes were offline, and it did not tell us which home broadband providers were filtering it. We wrote to all of them anyway.
The Fix: Reclassification Under the BBFC Framework
There is a proper process for this, and it is faster than I expected. Under the BBFC’s appeals procedure, anyone with an interest in a site, including its owner or its developer, can ask a mobile network to review how it is classified. The network has up to five working days to respond. If it refuses, the BBFC will adjudicate, normally within another five working days. The BBFC publishes the address each network uses for these requests, and the Open Rights Group’s guide for site owners walks through the same two stages.
We sent the requests on Sunday evening, one to each network, from our agency address on the shop’s behalf. Each one said who we were, what the shop sells, when the platform changed, and linked the public blocked.org.uk result as evidence. We wrote to Three, O2, EE, Vodafone, BT Mobile and Tesco Mobile, and to Internet Matters, which takes these requests to BT, Sky, TalkTalk and Virgin Media for home broadband.
| Network | What happened | Outcome |
|---|---|---|
| O2 | Tested as cleared on Monday afternoon; the Online Harms team confirmed by email on Tuesday morning | Cleared in about one working day |
| Three | First replied that the site was categorised as Business and Commercial and not blocked; our probe still showed the 18+ page that afternoon, so we sent the evidence back | Cleared the next day; confirmed in writing two days later |
| BT | Replied that the site was already categorised as Online Shopping and Clothing and not blocked on BT | Never blocked on BT |
| EE | No written reply; tested by a colleague of the owners on an EE phone | Loads normally |
| Vodafone | Acknowledged and opened a review | Still pending when we published |
| Tesco Mobile, Internet Matters | No reply | No reports of blocking from either |
Three deserves its own paragraph, because it is the lesson in how to work with these teams. Its first reply, on Monday, said that the site loaded behind the filter and was correctly categorised. Its own filtered line was still returning the 18+ page that afternoon. We replied the same day with that fresh result and the control store passing beside it, and asked them to check both the bare domain and the www address for an older classification. On Tuesday a fresh test passed. Two days later Three confirmed that both addresses were correctly categorised. The difference between those two replies was evidence. A polite email saying “our site is blocked” gets a polite check; a dated test result from the network’s own filtered connection gets a fix.
While all this was going on, the owners still needed to see their own shop. On a personal line that is easy: lift the 18+ filter with the network’s age check. On a company line it often is not, which is a good reminder that plenty of your customers cannot lift the filter either, even if they wanted to.
After the Fix: UK Orders Back to Normal
The numbers since the networks cleared the site tell the story better than I can. In the six days between go-live and Three’s fix, the shop took six UK web orders, about one a day. In the eight and a half days after it, the shop took nineteen, about 2.3 a day, which is right back to the BigCommerce average of 2.2.
| Period | UK web orders | Per day | Over Three or O2 mobile |
|---|---|---|---|
| 23 Sep (go-live) to 29 Sep (Three cleared) | 6 | About 1.0 | 0 |
| 29 Sep to 7 Oct | 19 | About 2.3 | 2, both on Three |
| BigCommerce baseline, Jul to Sep 2026 | 183 in 84 days | About 2.2 | Not recorded |
The detail I like most is in the last column. Before the fix, not one UK order arrived over Three or O2. In the first week after it, two arrived over Three’s own mobile network, the network that had been blocking the shop only days earlier. Those are customers who would have seen a certificate error and gone elsewhere.
I would not put a precise figure on the lost sales. These are small numbers over a short period, the first days after any launch are noisy, and some UK mobile customers will have come back later on Wi-Fi. But the direction is unambiguous, and so is the arithmetic of a UK order rate that halves on launch day and recovers the day the filters clear. On a larger store, or over a longer period before anyone noticed, the same block would have cost real money.
Why a Platform Move Can Trigger a Reclassification
The question every merchant asks next is why this happened at all. Nothing on the shop is adult content, the catalogue was the same on Shopify as on BigCommerce, and the site had passed every UK filter in 2017. Here I have to be honest that nobody told us, and the networks do not publish how their classification vendors work. What we can say is what changed.
A platform migration changes almost everything a classification system can see about a site at once. The IP addresses move to a new provider. The certificate is new. The page structure, the scripts and the wording all change. Many filtering systems combine a domain’s reputation with an automated look at its content, and a domain whose hosting suddenly changes is exactly the kind of signal that prompts a fresh look. If that fresh look happens while certificates are still issuing, or lands on product titles like “Kids With Guns” or “Bomb Hugger” without the context that they are Banksy artworks, a site can be reclassified without anyone intending it.
That is my inference, not a vendor’s statement, and I would not treat it as proven. The practical conclusion does not depend on it, though. Any UK store that changes platform, hosting or domain can come out the other side with a classification it did not have before, and the only way to know is to test from the networks themselves. It is not a Shopify problem, either: the same thing could happen to a store moving onto BigCommerce, WooCommerce or anywhere else, and it can happen to a store that sells nothing remotely controversial.
- Stores we would test first. Anything with artwork, slogans, alcohol, knives and tools, vaping, lingerie, health products, or product names that read badly out of context.
- When it bites. Straight after a domain or hosting change, when a classifier takes a fresh look.
- Who notices first. Usually the owner, on their own phone, and usually not until a few days in.
- Who never notices. Customers, who simply see a security error and leave without telling you.
A Quick Overview of Ruby Digital Agency (and Why We Care)
For readers meeting us for the first time: Ruby Digital Agency is a Shopify Plus Partner that does one thing on purpose. We move brands onto Shopify and Shopify Plus and make the move pay for itself. We have completed more than a hundred migrations, from BigCommerce, WooCommerce, Magento, OpenCart, Weebly and custom builds, for brands in the UK, the US, Canada, Australia and Europe. Every migration is done in-house: we extract the source data, enrich it through the old platform’s API and import it through Shopify’s Admin API, then reconcile every record against the source before launch. Recent case studies include inlinePRO’s BigCommerce to Shopify migration and SoSlanty’s move from Weebly.
| Service | Who it is for | Typical timeline |
|---|---|---|
| Standard Shopify Migration | Mid-market brands, $2M–$20M/yr | 4–8 weeks |
| Shopify Plus Replatforming | Enterprise brands, $20M+/yr, from Magento, Adobe Commerce or custom builds | 6–8 weeks |
| Multi-Store & Subscription Integration | B2B wholesale, subscriptions, multi-brand architectures | Scoped per project |
| Ecommerce Website Audits | Any platform: Shopify, WooCommerce, BigCommerce, Magento, custom | Fixed-scope engagement |
| SEO and AEO | Brands that need to be found in Google and cited by AI assistants | Ongoing |
| Shopify POS Implementation | Retailers uniting stores and online | Scoped per project |
The economics are why brands call us. Across our migrations, clients recover the investment in under 18 months, see conversion rates about 15% higher on average, and cut total cost of ownership by around 29%; infrastructure costs alone fall by as much as 80% when a self-hosted stack goes away.
Why we care about this one: a migration is only finished when every customer can reach the new store, and this was a failure mode that no amount of data reconciliation would have caught. We already check redirects, feeds, shipping rates and tracking at every go-live. Since The Banksy Shop, a UK network-filter test sits on that list too, run before the DNS switch and again the day after, for every client that sells into the UK.
A Seven-Step Filter Check for Any UK Store Launch
This is the check we now run. It takes about twenty minutes and costs nothing.
- Take a baseline before the switch. Submit your live domain to blocked.org.uk while it is still on the old platform. If it is already blocked somewhere, you want to know that before launch, not after.
- Check which probes are online. The probe status page shows which networks can be tested that day. Note the ones you cannot test, so you know where your blind spots are.
- Test the plain http:// address, not just https://. Over HTTPS a block only shows up as an SSL error. Over plain HTTP the filter can show its block page, and the result reads “blocked” with the network named.
- Run a control. Submit another store on the same platform and certificate chain at the same time. If the control passes and you fail, the block is yours; if both fail, it is the probe.
- Test again the day after the DNS switch. Use an address variation you have not tested before (a collection page works), because the tool reuses recent results for an address it has already checked.
- Watch the order mix for the first week. If UK orders drop while overseas orders hold, or every UK order arrives over home broadband and none over a mobile network, test immediately.
- If a network blocks you, ask it to reclassify with evidence. Use the address the BBFC publishes, link the public test result and a passing control, and follow up with a fresh test if the first reply says you are not blocked. Escalate to the BBFC after five working days.
Launching a UK store, or moving one to Shopify?
We run this check, alongside redirects, feeds, shipping and tracking, as part of every go-live, and we can run it on your existing store as part of an ecommerce website audit. Book a call and tell us what you are planning.
What Happens If You Do Nothing
If your store is blocked and you never check, nothing visible happens, and that is the problem. Your site stays up. Your monitoring stays green. Overseas sales continue, and UK sales from home broadband continue, so the total never falls far enough to set off an alarm. What disappears is the slice of your UK traffic that arrives on a phone with the default filter on, and for most UK stores that is a large slice.
The visitors you lose this way do not complain. They see a security warning, assume your shop is broken or unsafe, and buy from someone else. Some of them will be clicking your Google Shopping ads, so you pay for the visit and still lose the sale. If it has happened to you once, it can happen again at the next domain, hosting or platform change, and every week it goes unnoticed costs a little more trust as well as revenue.
The fix, when you find it, is free and fast. O2 and Three each cleared The Banksy Shop within about a working day of seeing the evidence. The expensive part is the time before anyone looks.
Frequently Asked Questions
What does this site can’t provide a secure connection mean?
It means the browser could not complete the secure HTTPS handshake with the website, and Chrome usually shows the code ERR_SSL_PROTOCOL_ERROR with the words sent an invalid response. Common causes are a certificate that is missing or still issuing, a wrong clock on the device, security software that inspects encrypted traffic, or, in the UK, a network content filter that is blocking the site and cannot show its own page over HTTPS.
How can I tell if a UK mobile network filter is blocking my website?
Submit your address to blocked.org.uk, the free tool from the Open Rights Group that tests through real UK connections with the default filters switched on. Test the plain http address as well as https, because over HTTPS a block only appears as an SSL error. Submit a control store on the same platform at the same time, and check the probe status page to see which networks were actually tested.
Why are UK mobile filters switched on by default?
Since 2013 the UK mobile networks have used a classification framework provided by the BBFC to restrict content suitable only for adults, and they apply it to every new line by default. An adult account holder can lift the filter by passing an age check, usually with a credit card in the network app or with photo ID in a store. Many adults never do, and work phones often cannot be changed by the user.
How do I get my website unblocked by Three, O2, EE or Vodafone?
Email the classification address each network publishes through the BBFC, explain what your site sells, and include evidence such as a dated blocked.org.uk result and a passing control store. The network has five working days to review it. If it refuses or does not respond, you can ask the BBFC to adjudicate, which normally takes another five working days. In our case O2 cleared the site within about a working day, and Three cleared it the day after we sent fresh evidence.
Does the block affect customers on Wi-Fi as well as mobile data?
It can. Mobile networks filter by default, many home broadband packages switch on a family filter for new customers, and public and hotel Wi-Fi in the UK is commonly filtered. Customers on home broadband who have switched the filter off will reach the site normally, which is why a partial block can hide behind orders that are still arriving.
Is this a Shopify problem?
No. The filters are run by the UK networks and their classification vendors, and they apply to any website on any platform. Shopify only came into it because the block appeared after the store moved there. A store moving onto BigCommerce, WooCommerce or any other host could see the same thing, and the check and the fix are identical wherever the store runs.
How long does reclassification take?
The BBFC framework gives each network up to five working days to review a request, with a further five for a BBFC adjudication if needed. In practice O2 cleared The Banksy Shop about one working day after our request, and Three cleared it the day after we sent fresh evidence from its own filtered connection. BT and EE were not blocking the site, and Vodafone was still reviewing it when we published.
How can I prevent this when I migrate my store?
Test the domain on blocked.org.uk before the DNS switch to get a baseline, test again the day after with a control store, and watch the share of UK orders that arrive over mobile networks during the first week. If anything is blocked, send each network a reclassification request with the evidence straight away rather than waiting for the problem to clear by itself, because it will not.
Final Thoughts
I have been moving stores between platforms for a long time, and I would not have guessed this one. A shop that sells Banksy T-shirts and canvas prints, with a valid certificate, a clean reputation and orders still arriving from abroad, was invisible to a large share of its own home market because a filter had quietly decided it was adult content. The error it produced is the most ordinary-looking launch error there is, and the instinct to wait for it to clear is exactly the wrong one.
What fixed it was not cleverness. It was the owners refusing to accept “give it time”, the order data pointing at a pattern, a free tool built by a digital-rights charity, and a control test that turned a theory into evidence the networks could act on. That combination took a few hours. The networks took about a day each.
So if you run a UK store and you are about to change platform, hosting or domain, add one line to your launch checklist: test the domain on blocked.org.uk before and after the switch. And if a customer ever tells you that your site can’t provide a secure connection on their phone, believe them, and test from their network rather than yours.
Planning a Move to Shopify or Shopify Plus?
We plan the strategy, run the heavy lifting in-house and verify every record against your source data before go-live, then check that every customer can actually reach the new store. Book a migration strategy call and we will map your move.
Related Reading
- BigCommerce to Shopify Migration Case Study: inlinePRO
- BigCommerce to Shopify Migration Guide (2026)
- Weebly to Shopify Migration Case Study: SoSlanty
- Google Shopping Feed Migration
- Shopify Market-Driven Shipping: What Changes and How to Prepare
- Ecommerce Website Audits
- More Shopify Guides on Our Blog
Lance Allison
Founder & CEO, Ruby Digital Agency
Lance Allison is the founder of Ruby Digital Agency, a Shopify Plus Partner that has completed more than a hundred migrations onto Shopify for brands in the UK, the US, Canada, Australia and Europe. He writes about what actually happens during replatforms, including the problems nobody puts in the checklist.