A landing page that opens for you can fail for one provider's customers, sometimes only on mobile data, while you keep paying for the clicks. Watch every URL a click passes through, per provider, at home and on mobile. When a block appears, pause that traffic first, then take a wrong block to whoever ordered it.
Why would a landing page fail for one provider's customers?
Because blocks and filters sit inside each provider's network or in the browser, and a test from your own connection shows only your own provider:
- Poland, gambling. Every Polish provider must block, in its DNS (which turns a domain into a server address), the domains on the Finance Ministry's register at hazard.mf.gov.pl. It also lists domains that advertise or promote illegal gambling, so a site promoting such an operator can be listed too (for gambling operators).Sources: Ministry of Finance, 28 March 2018 · Gambling Act of 19 November 2009 (consolidated text Dz.U. 2025 poz. 595), article 15f · register site, Act page, checked 11 November 2026
- Poland, Orange's own filter. Orange's CyberTarcza blocked 345,000 phishing domains in 2025, and Orange says it sometimes blocks a site by mistake. On an https page the blocked visitor sees a certificate warning: your page looks broken, not blocked.
- United Kingdom, mobile data. EE, O2, Three and Vodafone block content they class as 18+ by default, and only on mobile data. EE's default setting blocks dating sites; Three's business help page lists gambling among the categories it filters (United Kingdom).
- Norway, brand-new domains. Telenor's optional Nettvern+ filter judges sites by reputation, which Telenor says lets it block more scam sites under 3 days old. Test a newly registered domain there before launch.
- Browser warnings and ad review. Chrome users went past only about 1 in 4 malware and phishing warnings (red warnings and lost visitors), and Google Ads disapproves ads whose destination has been hacked. Chrome's "Did you mean ...?" warning compares the address with very popular sites, so a domain that resembles a popular site's address, or carries another site's full address inside its own, as in google.com.example.com, can trigger it.
Which URLs should you keep checking in each market?
Every URL a click passes through; a block on any one ends the visit:
- The landing URL exactly as the ad sends it. Path and query included: on a hacked site, Cloudflare usually puts its phishing warning in front of one URL, not the whole domain.
- Every tracking and redirect domain. If one is blocked, the visitor never reaches the landing page, and a blocked tracker may not record the click.
- The partner's destination. You do not control the offer page, but a block there loses the conversion you paid for.
- Each provider, at home and on mobile. In Poland, Orange, Play, Plus and T-Mobile apply CERT Polska's list of phishing and fraud domains; the UK mobile networks' 18+ filters touch mobile data only.
Is it a block, a broken page or the partner's bot protection?
If only one provider's customers get a notice page, "site does not exist" or a browser security error, that network most likely stopped the page. Failing everywhere, your connection included, means the page is broken. A "prove you are human" check, "access denied" or "not available in your location" usually comes from the site's own bot protection or geo rule, so ask the partner: rules that count visitors per IP address can shut out many phones behind one shared address (works on Wi-Fi, not on mobile data).
Sources: IETF RFC 6269, June 2011 · Cloudflare blog, 29 October 2025
Google Ads wants the landing page accessible in the targeted location and disapproves ads whose page shows an access-limitation message there or returns a 403 or 404. Its ad-review crawler, AdsBot, often crawls from the United States, so an approval says little about what Orange customers in Poland get.
Sources: Google Advertising Policies Help, Destination not accessible · Destination requirements, both checked 12 November 2026
| Orangehome | Blocked dns.redirectOrange's DNS sends this domain to a warning page, seen on 3 customers' connections in 2 parts of its network. Marked "likely". |
| Plusmobile | Site refused us target_policyThe site showed our test a "prove you are human" check: its own bot protection, not a block by Plus. |
What should you do when a provider blocks the landing page?
Pause the campaign, ad set or placement for that market or provider first. Then find who ordered the block; that decides who can lift it:
- Polish gambling register. The domain holder can object to the Minister of Finance within two months of the entry.
- CERT Polska's list. The domain holder objects to the head of UKE, Poland's telecom regulator, with a qualified electronic signature or a Polish government e-ID; a plain email is not enough. For Orange's own filter, write to cert.opl@orange.com.
- Norway's gambling list. Lotteritilsynet must lift a block when the site owner asks and the reason no longer applies.
- UK mobile 18+ filters. Ask the network first (Three: content@three.co.uk), then the BBFC, whose rules do not cover gambling.
- A red browser warning. Fix every listed page, then press Request Review in Search Console ("Deceptive site ahead" guide).
If the domain is the partner's, let them file; send them the market, provider, connection type, time and what visitors saw. If the block is right because the offer has no licence there, stop sending traffic to that market.
What linkspect answers for a campaign
linkspect opens the full URL through home and mobile connections of named providers in the countries open today, and answers per provider: opened, blocked and how, down everywhere, or the site refused our test. Each check also looks up the page and its domain in Google Web Risk (the commercial counterpart of Safe Browsing), Chrome's lookalike-domain rules and Google's Ad Experience Report. An API monitor repeats the check every 15 minutes to once a day and reports a change only after a confirming re-check, to a signed webhook your script can use to pause the campaign. Accounts get 20 monitors by default, early access is free, and an uncertain result says so. Get early access or read the API quickstart.