Stop Unwanted Website Notifications at the Permission
Find the website allowed to notify you, block its permission, and distinguish browser notifications from pop-ups, extensions, and fake security warnings.

TL;DR
- —Start in browser settings rather than following the warning in an unwanted notification.
- —In Firefox, blocking a site and removing its saved permission are different choices.
- —Stopping notifications is not a malware scan or proof that an account is secure.
A notification saying your computer is infected is a claim, not a diagnosis. Take the browser's settings route instead of the link in the alert. This walkthrough is for desktop Chrome and Firefox. Phone menus and managed work devices can differ. Chrome: find the allowed website Chrome's instructions put notification controls under Settings → Privacy and security → Site Settings → Notifications. Review the sites allowed to send notifications and block the one you no longer want. You can also change the default for future requests. Check the address carefully. Keep a permission you need for a meeting or messaging service; remove the unrelated one. This is a review of saved permissions, not a reason to blanket-approve familiar-looking names. Chrome also offers quieter permission requests. That changes how a request appears; it is not the same action as blocking an already allowed site. Pop-ups and redirects have a separate settings page. Firefox: choose Block or Remove Open Firefox Settings and find Notifications in its permissions section. The section label can vary by version. In the saved website list, choose Block for an unwanted sender and save the changes. Mozilla distinguishes that from Remove Website: removing a saved permission allows the site to ask again, while blocking it prevents a new request. The same panel has a separate option to block new permission requests. Firefox can receive a permitted site's push notifications while the browser is open even when that website is not loaded. Closing a tab is therefore not a reliable way to revoke permission. Do not treat the warning as your support desk The FTC's scam guidance describes fake security alerts and people posing as technical support. Do not call a number supplied by a surprise warning or grant someone remote access because the warning tells you to. When you need support, find the provider through a route you already trust. If you have already shared access or paid, use the FTC's incident guidance and the relevant provider's recovery process rather than continuing with the person who contacted you. Check the result without overclaiming Record the site you blocked and the browser profile you changed. A second profile or another browser is a separate place to inspect. If alerts continue, identify the application or browser shown as their sender before changing more settings. Blocking a permission does not establish whether software was installed, files were accessed, or credentials were exposed. Those are different questions. Our permission audit also cannot inspect another site's grants: it shows supported states for this site. For the next check, review extension access, or return to privacy resources. Avoid installing an unfamiliar “notification cleaner” just because an alert advertises one.
Sources
- Chrome Help: Use notifications to get alerts
Desktop notification controls and separate pop-up settings
- Mozilla Support: Web Push notifications in Firefox
Reviewing, blocking and removing notification permissions
- FTC: How to spot, avoid, and report tech support scams
Fake security warnings and remote-access scam precautions