First CHAppsWeb apps

First CH Apps / Will that Google link open without signing in?

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.

We never store the URL. The server uses only the file ID.

SampleA sample result for a fictional file. Google was not asked.Close the sample

Google Docs · ID ending …Smpl · asked once without signing in

Likely viewable without signing in

Anyone who has this link can probably view it without signing in — including people it gets forwarded to.

File name: 2026年度 提案資料(見本) (shown here only; never stored)

Before you send it

  1. Make sure anyone may see it

    If it contains confidential or personal data, set General access back to Restricted and add only the recipient’s email address.

    Google official help: Google Drive Help: Share files and folders and manage access

A line to share with your team

Checked before sending: the other side saw “Viewable without signing in”

This is what someone who is not signed in sees right now. We can’t check whether the recipient’s own account can open it. Google may answer the same way for files you can’t access and files that don’t exist.

Check another linkCheck the wording of your email (Japanese Business Tone Check)

Other sample results:Sign-in requiredNot found

How it works, criteria, what we send, API and sources

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.

How to use

  1. Open the file, choose Share → Copy link, and paste the URL (folder links work too).
  2. Press “Ask Google once, without signing in”. The result appears within seconds.
  3. If it says “Sign-in required”, work through the fixes below and check again.

What the four results mean

ResultGoogle’s first responseFor the recipient
Sign-in requiredRedirect to the sign-in page (accounts.google.com)Only people on the sharing list can open it after signing in
Likely viewable without signing in200 with a file name (og:title) in the first 64 KBAnyone with the link can probably view it
Not found404Wrong URL, deleted, or no permission to view
Can’t tellAnything else (redirect elsewhere, unexpected page, no answer in 5 s)Open it in a signed-out window to check

FAQ

Will “Anyone with the link” fix it?

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.

I added them, but they still see “You need access”

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.

Does “Sign-in required” mean they can’t open it?

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.

Do you read the file’s contents?

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.

My work account won’t let me choose “Anyone with the link”

Your organisation’s admin may have turned off external sharing. You can’t change that yourself, so ask your admin.

What this app does not do

  • Check services other than Google (Dropbox, OneDrive, Box and so on)
  • Check while signed in (whether the recipient’s account can open it)
  • Show or store contents, or change sharing settings for you
  • Check many URLs at once, or track who views a file

What is sent to the server, what is stored, and when it is deleted

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).

Sources (Google official help)

Checked 2026-11-18

Use it as an API

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.