Hi Vercel team,

Google Safe Browsing has flagged my protected Next.js Preview deployment as deceptive. Chrome displays “Dangerous”, and Google’s Transparency Report says “Some pages on this site are unsafe”.

The application is USTC, a sports tipping application using Supabase authentication. Deployment Protection remains enabled, and testing is paused while the cause is investigated.

I have already submitted Google’s public Safe Browsing review form and received confirmation of successful submission.

Vercel’s support assistant checked deployment metadata and configuration, reporting a successful build and no Vercel platform blocks. It clarified that this was not a source-code or dependency security audit. The cause of Google’s warning remains unconfirmed.

Search Console HTML verification requires public access to a verification file, and I cannot add DNS verification records for the Vercel-managed preview hostname.

What is the recommended investigation and review process for the existing flagged hostname while keeping Deployment Protection enabled? Can Vercel staff assist or provide a private channel for the deployment URL and identifiers?

I’m on the Hobby plan, and the Deployment Protection support category directed me here. I want to retain the existing hostname and protection, with production unchanged.

Thank you.