Public Surface Checker is a public evidence checker with two focused tools: a GitHub Anonymous Access Checker that reports redirects, login walls, status codes, GitHub Pages availability, timestamps, and limitations, and an App Store Lookalike Finder that presents explainable name, seller, bundle ID, icon, screenshot, and description similarity signals. Every run produces a dated evidence report you can copy or download — no account required.
On the first screen, pick a tool: the GitHub Anonymous Access Checker accepts a repository or GitHub Pages URL and reports redirects, login walls, status codes, GitHub Pages availability, timestamps, and limitations. The App Store Lookalike Finder accepts an app name or bundle ID and presents explainable name, seller, bundle ID, icon, screenshot, and description similarity signals against public Apple listing metadata. Paste your input into the Primary input field, run the check, and read the dated evidence report in the output panel — then copy it as text or export it as JSON.
Paste a public GitHub repository or GitHub Pages URL into the primary input and run the check. The GitHub Anonymous Access Checker reports the final destination after redirects, whether an anonymous visitor hits a login wall, the observed HTTP status code, whether GitHub Pages is available for the repository, and the timestamps of each observed hop. Every finding is reported as evidence with a stated limitation, so you can tell a verified redirect from a blocked page and an unverified guess.
Enter an app name or bundle ID and the App Store Lookalike Finder queries public Apple listing metadata. The report presents explainable similarity signals across name, seller, bundle ID, icon, screenshots, and description, with per-signal scores and the exact public strings used for each comparison. The tool describes what is similar and why; it never alleges fraud, copying, or intent on the part of any developer.
Both tools share one evidence-report framework. A report always records the input, the checks performed, the observed findings with status and detail, the timestamp of the run, and the limitations of the check — for example whether a login wall was detected by status code, by redirect pattern, or by page content. Reports are generated deterministically in the browser from public metadata and can be copied as text or exported as JSON for your own records.
All analysis runs locally in your browser against public metadata. No account, sign-in, or payment is required, and checks are only as current as the public metadata they read. If the live evidence service is unreachable, the tool clearly labels the run as a local deterministic simulation so the report never overstates what was verified. You decide what to do with a report — the tool never publishes anything on your behalf.
It checks the final URL after redirects, whether anonymous visitors are stopped by a login wall, the observed HTTP status code, whether GitHub Pages is available for the repository, timestamps of observed hops, and the limitations of each finding. Detection is based on public request metadata and page behavior, not on an account.
No. The tool reports explainable similarity signals — name, seller, bundle ID, icon, screenshots, and description — with the exact public values used. Similarity is descriptive evidence, never an allegation of fraud or copying intent.
No. Both tools run from the first screen without sign-in, and every report is generated locally in your browser.
Results reflect the public metadata observed at the time of the run. Each report carries a timestamp, and reports always state the limitations of the checks they contain so stale or unverifiable signals are not presented as fact.
Yes. Every report can be copied as text or exported as JSON from the output area. The tool never posts a report anywhere; sharing is always your own action.