shortscheck your own page

the in-app browser report

sign-in buttons that die inside Instagram

We read the signup page of 236 products, one HTML fetch each, and listed every third-party sign-in button on it. Then we said what that button does inside an in-app browser.

196 of 236 pages offer a sign-in that cannot complete there at all. That is 83.1% of the pages we could read.

pages read
236
one fetch each
cannot complete
196
Google, Microsoft, Facebook
loads, degraded
9
no session, no autofill
no third-party sign-in
31
in the HTML we read

last read 28 Sep 2026, 15:25 UTC · 133 more pages gave us no readable HTML and are not listed · 32 addresses we tried no longer exist

these numbers are version 18, published 28 Sep 2026, 15:27 UTC. They will not change. cite this version

these pages pay for the taps they lose

We read the same pages a second way, looking only for evidence that someone buys the taps arriving on them. A Google Ads conversion id, a Meta or TikTok pixel, an affiliate network, or their own code reading a gclid.

66 of the 189 pages we screened whose sign-in cannot complete carry one. That is 34.9% of them paying for a tap that arrives at a sign-in button which cannot complete. The pages that only degrade sign-in are not counted here.

A tag means the tag was there when we read, not what it spends. Every shorts link carries whatever you add to the end of it through to the destination, so a gclid or a via still arrives after the escape.

which button, on how many pages

  • sign in with Google

    170 of 236 pages · 72%

    Google refuses OAuth inside an embedded browser and answers disallowed_useragent. The button does nothing anyone can fix from the page.

  • sign in with Facebook

    52 of 236 pages · 22%

    Facebook login is unsupported inside an embedded browser, including Facebook's own.

  • sign in with Apple

    33 of 236 pages · 14%

    Apple's sign-in needs a popup, and in-app browsers commonly refuse to open one.

  • sign in with GitHub

    32 of 236 pages · 13.6%

    GitHub loads, but with no saved session the person types a password and a 2FA code from memory.

  • sign in with Microsoft

    21 of 236 pages · 8.9%

    Microsoft requires a real browser for its sign-in and rejects embedded ones outright.

  • sign in with X

    6 of 236 pages · 2.5%

    X loads, but with no saved session the person types a password from memory.

  • sign in with Discord

    1 of 236 pages · 0.4%

    Discord loads, but with no saved session the person types a password from memory.

cannot complete inside an in-app browser

196 pages

At least one sign-in button on this page answers a refusal rather than a login.

check your own page

Paste your signup, login or checkout page. We read it once and name every button that cannot complete. No account, and your result has its own shareable page.

we read the page once and tell you what breaks. free, no account, nothing stored about you.

A shorts link reopens your page in Chrome or Safari, where the session lives, and counts every tap. free keeps 5 links and 30 days of taps. shorts Lifetime is $49 once.

how we read these pages

Every row above is also free open data, as one JSON or CSV file. Use it in anything, and say where it came from.