Pewterkit Check · Sign-in

Does Google’s sign‑in show your domain?

If Google’s sign-in screen says “continue to your-app-1234.firebaseapp.com” or “xxxx.supabase.co”, your users see an address they don’t know. Check yours free, then get the fix for your stack.

Free scan · pay only for the fixes you pick · See a sample report

Your launch check

0passed
0to fix0worth fixing0passed
$0 ·
Pick the categories you want fixedPick the categories you want fixed

Filled-in fixes for your builder · 30 days of re-checks · money back if our re-check can't confirm the fix within 14 days

Every finding comes with its evidence.

The exact line, header or record we read on your live site. Every check is tested against a broken site and a healthy one before it ships, and you can confirm every fix you buy with a re‑check.

What the sign-in check reads

One free scan covers all six categories; this page puts Sign-in first.

  • The name Google showsWhether Google’s sign-in screen names your own domain, your Firebase project’s firebaseapp.com address or your Supabase project’s supabase.co address.
  • No development keysClerk test keys, Auth0 development tenants or Firebase emulator settings on the live site.
  • No localhost linksSign-in and email links that still point at localhost.
  • Ready for Google brand verificationPrivacy policy and terms linked from your home page, so Google can show your app’s name and logo.

Sign-in fixes come as Signhome, by Pewterkit, in the same checkout as the other five categories.

Why it matters

Google names the address that handles sign-in. Until that address is your own domain, people see your platform’s address at the moment they decide whether to trust your app.

All six checks, in the same scan

Pick the categories you want fixed, or take all six. One payment.