[Production Outage] Custom domains redirect to SafeBrowse

Help
,
1

Issue Summary

Our custom domains are being redirected to SafeBrowse instead of serving our application. This is a Vercel infrastructure issue, not DNS misconfiguration.

Affected Domains

  • :cross_mark: foodshare.club
  • :cross_mark: www.foodshare.club
  • :cross_mark: test.foodshare.club
  • :white_check_mark: foodshare-dev.vercel.app (works perfectly)

Technical Evidence

DNS Resolution:
http://www.foodshare.club → 329e303e79a7dae5.vercel-dns-017.com
Resolves to: 64.29.17.65, 216.198.79.65

Raw response on port 443:
HTTP/1.1 302 Found
Location: Potential Threat Detected

These Vercel edge IPs are serving plain HTTP redirects to SafeBrowse on port 443 instead of performing TLS handshake.

SSL Error:
curl: (35) error:1404B42E:SSL routines:ST_CONNECT:tlsv1 alert protocol version

My Location

  • IP: 98.238.135.19
  • ISP: Comcast (AS7922)
  • Location: California, US

What I’ve Tried

  • Removed and re-added domains in Vercel dashboard
  • Added new test subdomain - same issue
  • Flushed DNS cache
  • Verified no CAA records blocking certificates
  • All domains show “Valid Configuration” in dashboard

Impact

  • 4,350+ users cannot access our non-profit food sharing platform
  • Community members who rely on shared food resources are affected

Vercel Support Response

Vercel support confirmed this is an infrastructure issue affecting specific edge nodes, but Hobby plan cannot submit support tickets.

Request

Please investigate why edge nodes 64.29.17.65 and 216.198.79.65 are serving SafeBrowse redirects for foodshare.club instead of our application.

Project: foodshare
Framework: Next.js 16
Plan: Hobby

4

Hey! Are you still seeing this? Your site works fine for me.

5

Hey @organicnz, just checking in to see if you’re still experiencing the redirect issue with your custom domains. Let me know if you need any further assistance or if everything’s resolved on your end.

6

Hey, @pawlean!

I hope you are doing super well! Deepest apologies for the late response, and thank you for the follow‑up.

The issue has been resolved on my end. Custom domains are now routing correctly and serving the app as expected. Appreciate you checking in.

7

Thrilled to see this! see you around the community :slight_smile:

8

Thank you so much for your kind greetings. Happy to join in :slight_smile:

9

The issue was resolved by submitting our domain for security review through Google Search Console:

After requesting a review, the SafeBrowse redirects stopped and SSL started working correctly. If you guys are experiencing this issue, verify your domain in Search Console and check for any flagged security issues there.

To send your domain to Google Safe Browsing for review, log in to Google Search Console, navigate to Security & Manual Actions > Security Issues, and click “Request a review” after fixing malicious content. Ensure your site is clean, as the review process can take up to 72 hours.