Window Defender blocks my test webpage and I don't know why?

firestats 76 Reputation points
2024-04-25T17:11:24.9666667+00:00

I need help. I am learning webpages on my own personal azure trail account for 30 days.
Microsoft defender seems to block my test webpage to test how embedding works, but I cannot tell why.

This currently only seems to be an issue on Bing as chrome and Mozilla report no errors:
Error code

I have tried reaching out to Window Defender feedback, but I have heard back yet. So I submitted another request and before that I went through the following steps:

  1. Upgraded all the javascript packages to the latest versions and check each package in case there were any security vulnerabilities
  2. Added a Content Security Policy
  3. Made sure the default SSL key is a valid external SSL
  4. Checked the website across 14 different website checkers to make sure there were no security issues. In fact the whole purpose of the test pages was to test alternatives to 3rd Party cookies.

I have done everything I can, but it still shows blocked in Bing.

Can anyone help?

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
37,798 questions
0 comments No comments
{count} votes

Accepted answer
  1. MudassirKakingray 75 Reputation points
    2024-06-28T10:53:51.03+00:00

    Hi,

    From the warning, you can choose to report this site as a safe site. Click the link for More information then click Report that this site does not contain threats.

    Additionally, you can also do the following:

    • If you ask users for personal information, use HTTPS with a valid, unexpired server certificate issued by a trusted certification authority.
    • Make sure that your webpage doesn't expose any cross-site scripting (XSS) vulnerabilities. Protect your site by using anti-cross-site scripting functions such as those provided by the Microsoft Anti-Cross Site Scripting library.
    • Use the fully-qualified domain name rather than an IP-literal address. (This means a URL should look like "microsoft.com" and not "207.46.19.30.")
    • Don't encode or tunnel your URLs unnecessarily. If you don't know what this means, you probably aren't doing it.
    • If you post external or third-party hosted content, make sure that the content is secure and from a known and trusted source.
    0 comments No comments

0 additional answers

Sort by: Most helpful