How to Fix Cloudflare Error 1012 (Access Denied)
What Cloudflare Error 1012 means
Cloudflare's 1xxx error family covers DNS, proxy, and security configuration problems, and Error 1012 is the one titled "Access Denied." It appears when the website owner's security settings forbid access based on malicious activity detected from the visitor's computer or network. Per Cloudflare's own documentation, the most likely cause is a virus or malware infection on the visitor's computer generating the suspicious traffic that tripped the site's defenses.
This is an important distinction from the other Cloudflare errors. A 521 or 522 means the site's own server is failing; a 1001 means DNS is misconfigured. Error 1012 means everything is working fine and you have been deliberately turned away. The block is aimed at your IP address or network reputation, not at the site's infrastructure, which is why clearing your cache, reinstalling your browser, or waiting for the site to "come back" does nothing. And because the decision belongs to the site owner's security configuration, Cloudflare's support team explicitly states it cannot override it — the only path to the site runs through the owner.
Common causes
- Malware or a virus on your computer: Cloudflare's own documentation names this the most likely cause. An infected machine quietly generates spam, botnet traffic, or attack patterns, and the site's security rules correctly identify your IP as a source of malicious activity. This is the first thing to rule out, not the last.
- Another infected device on your network: Cloudflare sees your public IP address, so the flagged traffic can come from anywhere behind your router — another family member's laptop, a phone, a smart TV, or an IoT gadget like a camera running bot malware. Your computer can be spotless while a compromised device on the same Wi-Fi gets the whole household blocked.
- Automated tools and scrapers on your connection: scraping scripts, auto-refreshers, SEO audit tools, download managers, and misconfigured VPN exit nodes generate exactly the request patterns security rules are built to catch. Even legitimate tooling can push you over the line if it hammers the site faster than a human could.
- A previous tenant of your IP address: home internet connections share IP ranges, and many ISPs hand out dynamic addresses. If the previous holder of your current IP was infected or abusive, the block can attach to you the moment the address rotates to your router. Restarting the router sometimes draws a cleaner IP.
- The owner's security settings are set too aggressively: site owners sometimes run their Cloudflare security level at its maximum, or write firewall rules that block whole countries, hosting ranges, or traffic patterns that include legitimate visitors. If your devices are clean and several of your devices fail from different networks, the block is a false positive on the owner's side.
How to fix Error 1012 — step by step
Steps 1 through 6 are for visitors. Step 7 is for the site owner.
- Confirm Error 1012 is a block against you, not an outage. Error 1012 is a deliberate access-denied page: Cloudflare blocked your request because the site owner's security settings detected malicious activity from your IP address or network. Try the same site on your phone using mobile data. If it loads there, the block is aimed at your computer or home network, and the visitor steps below apply. If every device fails everywhere, the block is broader and you should still contact the site owner — this is never a server outage or a broken link.
- Update your antivirus software and run a full scan. Cloudflare's own resolution starts here because a malware or virus infection is the most likely cause of the flagged activity. Update your antivirus definitions, then run a full system scan rather than a quick one, and also run a second-opinion scan with a free on-demand tool such as Malwarebytes. Remove anything found and restart your computer. Do not skip this step: an infected machine keeps generating the suspicious traffic that triggered the block, so contacting the site owner before cleaning up will not help.
- Secure your network: check other devices and your router. Cloudflare flags the public IP, so the offending traffic can come from any device on your network — another computer, a phone, a smart TV, or an IoT gadget infected with bot malware. Scan the other computers on the network, disconnect anything you don't recognize, and log in to your router admin panel to change a weak or default password. If a family member's device or a compromised camera is the source, your clean computer gets blocked too.
- Restart your router and stop running scrapers or bots. Turn off any scrapers, auto-refreshers, SEO tools, VPN exit nodes, or download managers on your connection, since automated requests are a common trigger for the malicious-activity flag. Then restart your router — many home internet plans assign a fresh public IP address on reconnect, which can clear the block if the old IP carried a bad reputation. If your IP is static, this won't change it, but the reboot is harmless and often resolves transient flags.
- Test from a clean browser on a different network. Before contacting anyone, prove your side is clean: open the site in a private window on a different network, such as your phone's mobile data with Wi-Fi turned off. If the site loads there, your device and network are no longer producing suspicious traffic, and the remaining step is getting the old block lifted. If it still fails on mobile data, the block may apply to a wider range or your account, so note exactly when it started and what error text you see.
- Contact the site owner and ask them to allow your IP. Cloudflare cannot override the site owner's security settings, so only the owner can unblock you. Find a contact address on the site's social media profiles or WHOIS record — the 1012 page blocks the site itself, so you cannot reach their contact form. Write a short message: you are a legitimate visitor seeing Cloudflare Error 1012, you have cleaned your devices and network, and you are requesting that your IP address be allowed through their firewall or security rules. Include your public IP address (search "what is my IP" on another device) and the time you first saw the error.
- Site owner: review and adjust the rule that blocked the visitor. If you run the site, open the Cloudflare dashboard, select the domain, and check Security then Events for the blocked request — the rule name and reason appear there. If it is a firewall rule you created, add an Allow rule for the visitor's IP or relax the rule's action from Block to Challenge. If Bot Management flagged them, consider Manage Challenge rather than block for their traffic pattern. And if the "malicious activity" was a false positive, confirm your security level isn't set higher than your site actually needs.
Did this fix it? Quick checklist
- A full antivirus scan came back clean on every computer you own
- The site loads from a different network, proving your traffic is no longer flagged
- Your public IP address is ready to include in your message to the site owner
- If you own the site, Security, then Events shows which rule fired, with an Allow rule in place for the visitor
If the owner allowed your IP and you still see Error 1012, double-check that they allowed the right address — people routinely paste their local network IP (192.168.x.x) instead of their public one, which changes nothing. Also confirm the rule is active in the correct zone if the site holds multiple domains, and wait a few minutes for dashboard changes to propagate. And if you are the owner and the flagged traffic never stops, take the malware angle seriously: an attacker may actually be spoofing your visitors, in which case your firewall rules deserve a closer look rather than a quick Allow.
Frequently asked questions
What does Cloudflare Error 1012 mean?
Error 1012 is Cloudflare's Access Denied page. It means the website owner forbids access based on malicious activity detected from the visitor's computer or network. In Cloudflare's documentation, the most likely cause is a virus or malware infection on the visitor's computer that is generating suspicious traffic. The site's security settings made the call, and Cloudflare cannot override them.
Can Cloudflare support unblock my Error 1012?
No. Cloudflare states explicitly that it cannot override the security settings the site owner has set for the domain. The block was created by the owner's configuration, so only the owner can allow your IP address back in. Contact the site owner directly — through their social media or email found via the domain's WHOIS record — and mention that you are seeing Cloudflare Error 1012.
Why am I blocked if I never did anything suspicious?
The block targets your IP address or network, not necessarily your computer. An infected device elsewhere on your home network, a neighbor sharing the same connection, a previous resident of your IP address range, or malware quietly running in the background can all generate the traffic that triggered the flag. Cloudflare sees a bad reputation attached to the IP and blocks everyone using it.
Will a VPN fix Cloudflare Error 1012?
It might let you reach the site, because you appear from a different IP address — but it is a workaround, not a fix, and many sites also block known VPN exit IPs. More importantly, it leaves the real problem untouched: if your device or network is generating malicious activity, that should be cleaned up anyway. Scan your devices first, and only use a different network as a diagnostic step before contacting the site owner.
I own the site — why did my visitor get Error 1012?
Your Cloudflare security settings flagged the visitor's network for malicious activity. Check Security, then Events in the Cloudflare dashboard to see exactly which rule fired. Often it is a strict firewall rule or an elevated security level catching false positives — for example, a visitor behind a shared office IP or a compromised ISP range. The fix is to add an Allow rule for their IP, switch the action from Block to Challenge, or tune the rule that is over-firing.