First CH Apps / Will that Google link open without signing in?
Paste a Google Drive, Docs, Sheets or Slides share link to see whether someone who is not signed in can open it (sign-in required / likely viewable by anyone / not found), with fixes linked to Google's official help.
See an exampleShows a sample result for a fictional file
Check before a client replies “I can’t open the file”. Paste one Google Drive, Docs, Sheets or Slides share link and our server asks Google once, without signing in, then tells you what the other side will see. If they can’t open it, you get the fixes in order, starting with adding their email address.
| Result | Google’s first response | For the recipient |
|---|---|---|
| Sign-in required | Redirect to the sign-in page (accounts.google.com) | Only people on the sharing list can open it after signing in |
| Likely viewable without signing in | 200 with a file name (og:title) in the first 64 KB | Anyone with the link can probably view it |
| Not found | 404 | Wrong URL, deleted, or no permission to view |
| Can’t tell | Anything else (redirect elsewhere, unexpected page, no answer in 5 s) | Open it in a signed-out window to check |
It will open without signing in, but anyone the link is forwarded to can see it too. For confidential or personal data, add the recipient’s email address instead.
They are usually signed in to a different Google account (for example a personal Gmail). Ask them to switch to the account you shared with.
If their Google account is on the sharing list, they can open it after signing in. This app only checks what a signed-out person sees.
We only look for the file name (og:title) in the first 64 KB of the first response. We return no contents, and the file name is only shown on your screen.
Your organisation’s admin may have turned off external sharing. You can’t change that yourself, so ask your admin.
What you send: one URL. The server extracts only the file type, the ID and the resourcekey (some files won’t open without it) and discards the rest of the URL (other query parameters, /u/0/ and so on).
The request: we put the ID and resourcekey into a fixed URL on docs.google.com or drive.google.com only, and send Google a single GET with no sign-in cookies. We don’t follow redirects; we look at the first response only, with a 5-second and 64 KB limit.
What we return: the status, the file name (shown on screen only), the fixes and official help links. We never return the fetched page itself.
Storage: the URL, ID, resourcekey and file name are not stored anywhere. Responses are no-store, so they are not cached, and they are not written to access, analytics or error logs. Everything is gone from memory when the request ends.
Limits: 5 requests per minute per IP. To count them, the IP stays in server memory for about a minute at most and is never stored.
Page views are counted with Google Analytics (the URL field is not sent).
Checked 2026-11-18
POST JSON ({"url": "https://docs.google.com/document/d/…/edit"}) to /hondai-wariai/api/check to get the same verdict (login, public, not_found or unknown) and fixes as JSON. 5 requests per minute per IP.