t3.storage.dev flagged as dangerous

I recently switched my app from using a custom domain for Tigris to t3.storage.dev to achieve the best performance endpoint. My users are primarily outside the Fly.io network, and custom domains only work with the Fly.io-optimized domain.

Now, my users are reporting that they cannot download files because the domain is flagged as dangerous. I have confirmed this issue myself.

Since I created the custom domain long before t3.storage.dev existed, I named it to match my subdomain (sub.mydomain.com). This means I cannot access it using the subdomain format due to the dots in the name.

What is the solution? Do I need to create a new bucket and migrate everything to use bucket.t3.storage.dev and hopefully avoid the blocking issue? I would like to avoid this if possible, so please suggest a better solution.

If you are talking about the below

This is because Google have marked the domain as dangerous

Hi @userbradley Thanks for the report. We have been notified about it and took action on it and requested Google to review the new state. It will be marked as safe soon.