> ## Documentation Index
> Fetch the complete documentation index at: https://wiki.lumiweb.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# Clear red warning screens

> Clear the red Google and Cloudflare warning

If your domain has already caught a red warning, the landing page has most likely made it into a database fed to automated scanners. **Before clearing the warning, rework the page (or, better, swap the landing page entirely)** — otherwise the warning will come right back. For how to lower the risk ahead of time, see [Avoiding bans](/en/domains/anti-block).

## Via Google Search Console

<Steps>
  <Step title="Open Search Console">
    Go to [search.google.com/search-console](https://search.google.com/search-console/welcome).
  </Step>

  <Step title="Add your domain">
    Enter the domain under **Domain property** → **Continue**.
  </Step>

  <Step title="Verify ownership">
    Add the suggested TXT (or CNAME) record. For how to create records, see [DNS records](/en/domains/dns).
  </Step>

  <Step title="Open the security report">
    After verification, a line about security issues will appear — open the **Full report**. It shows which pages contain the prohibited content.
  </Step>

  <Step title="Remove the content">
    Delete the flagged pages or replace them with a 404 stub.
  </Step>

  <Step title="Request a review">
    Write something like "Content was deleted" and submit a request for re-review.
  </Step>
</Steps>

<Note>
  The warning usually disappears within **24 hours**, and you get an email notification. If that doesn't help, message [@lumisup\_robot](https://t.me/lumisup_robot) and include the domain.
</Note>

## If Cloudflare is showing the warning

The red warning page can be shown by **Cloudflare itself** when the domain is proxied through it (the orange cloud) and has been caught by its filter. The fix is to **remove proxying**: traffic will then go straight to your server, bypassing Cloudflare, and its warning page will stop appearing.

<Steps>
  <Step title="Open DNS settings">
    [@lumibp\_bot](https://t.me/lumibp_bot) → **My Domains** → your domain → **DNS settings**.
  </Step>

  <Step title="Find the proxied records">
    These are the records with **proxying enabled** — the orange cloud. Usually the root A record and `www`.
  </Step>

  <Step title="Turn off proxying">
    For each such record, switch proxying to **off** — the cloud turns gray (DNS-only mode). Cloudflare will stop sitting between the visitor and the server.
  </Step>

  <Step title="Wait for propagation">
    Within a few minutes the change will spread and the warning will be gone. To check, see [When it goes live](/en/domains/propagation).
  </Step>
</Steps>

<Warning>
  Without proxying you lose Cloudflare's protection: the server's real IP is exposed, and its DDoS shield and SSL are switched off. Install **your own certificate** on the server in advance, or HTTPS will throw an error — see [SSL and Let's Encrypt](/en/vps/ssl).
</Warning>

<CardGroup cols={2}>
  <Card title="Avoiding bans" icon="shield-halved" href="/en/domains/anti-block">
    How to avoid a red warning in the first place.
  </Card>

  <Card title="Cloudflare" icon="cloud" href="/en/domains/cloudflare">
    SSL modes, redirects, protection settings.
  </Card>
</CardGroup>