NEW RESEARCH: WHY SHIELDIFY MOVED TO AWS.Read the report Sign in
Changelog

What's New at Shieldify

Customer-facing improvements, newest first.

17 November 2026Fewer alert e-mails while an attack comes and goes, and our team can now open a support ticket for you.

Notifications

  • An attack that comes back in short waves no longer fills your inbox. A wave that starts within an hour of the last one ending sends no e-mail, neither when it starts nor when it ends. Discord still gets every wave.
  • Automatic mode switching on or off is no longer e-mailed. It still goes to Discord if your website has a webhook.

Support

  • Shieldify's team can now open a support ticket for you, for example when your DNS records need a change. You get an e-mail with the message and can reply in the support center.
11 November 2026New Intrusion Reports show who tried to break into your website, what they tried, and what the firewall did about it; Fallback Pages keep your website up while your server is down; and updates to our edge no longer interrupt websites.

Fallback Pages

  • New: when your website's server does not answer, visitors see the last copy Shieldify kept of the page instead of an error page, with a bar at the top saying your website is not responding, when the copy was saved, and a button to try again.
  • The bar stays at the top of the window while visitors scroll, never covers the page's own content, carries the Shieldify logo, and can be closed.
  • Only pages shown to visitors who are not signed in are kept, never a page that sets a cookie or asks not to be stored, and never an address with a query (such as a link carrying a token). Copies are kept for 7 days.
  • On for every website. You can turn it off under Caching, where you also see how many pages are kept; purging the cache removes the copies too.

Intrusion Reports

  • New: every website has an Intrusion reports page. When someone scans your website for weaknesses, the attempt becomes one report: the addresses with their country and network, the kinds of attack they tried, the tool they used when it can be told (such as Burp Suite, Nuclei or sqlmap), where they put their payloads, the pages they went for, and how many requests the firewall refused.
  • When a scan is over, you get an e-mail, and a Discord message if your website has a webhook. Bots that try known exploits or look for exposed files, as they do across the internet, are listed without an alert. You can turn the alert off under Notifications.
  • Scanners often put an address of their own into a request to see whether your website contacts it. Such a request is not an attack on its own and reaches your website; the report now shows these requests and where they were, so you can check that your website does not fetch addresses it is given.
  • Attempts since 13 October 2026 are already listed.
  • The weekly report now counts the week's break-in attempts.

Reliability

  • Updates to Shieldify's edge no longer interrupt your website. Until now, for about 15 seconds during each update, new visitors had to wait for your pages. Now the new version starts and takes over first, while the old one finishes the downloads and connections it already had. In our measurement during an update, not one of over 3,500 requests failed.
  • Fixed: a secure connection that opened at the very moment of an update could be closed before its first request, and the visitor saw a connection error. It now gets its request answered.
10 November 2026The firewall now reads request bodies the way your application does and checks them to the end, uploaded images that hide server code are blocked, and floods that misuse HTTP/2 are stopped earlier.

DDoS protection

  • Floods that misuse HTTP/2, such as Rapid Reset and CONTINUATION floods, are now stopped at our network edge within seconds, before their connections cost any further work. None of their requests reached websites before either; now they are stopped sooner.

Firewall

  • JSON and XML bodies are now checked to the end, however many fields they hold. Until now only the first part of a very large JSON body was checked.
  • A JSON body is now checked the way your application reads it, also when it comes in an unusual encoding. A JSON or XML body the firewall cannot read at all is blocked instead of let through.
  • Very large JSON requests are checked up to three times faster.
  • Fixed: when the firewall was very busy, a request it could not finish checking in time could be let through. It is now refused, and the visitor can try again.

Upload Protection

  • New: uploaded images that hide server code, such as a web shell disguised as a picture, are blocked before they reach your website. Documents and text files are not affected.
  • Each image format (JPEG, PNG, GIF, WebP, SVG and others) has its own rule under "Shieldify Upload Protection" in your website's firewall settings, so you can switch one off if your website really stores code in images.

Connections to your server

  • A request that carries a body now closes its connection to your server afterwards. Something hidden inside such a request can no longer reach another visitor, even if your server reads the body incorrectly. HTTP/2 connections to your server are not affected.

Dashboard

  • Your website's firewall settings now list only the categories you can change. The firewall's internal parts still run, they are just no longer shown.
  • Fixed: adding a domain that has no DNS records showed a general error. It now tells you that the domain has no DNS records yet.
  • Fixed: some errors showed a general "Failed" message instead of their own, for example when you tried something too often and had to wait.
9 November 2026The firewall can no longer be talked past with specially built requests, and one client can no longer make it work unusually hard for everyone else.

Firewall

  • Requests built to make the firewall's rules miss an attack are now blocked instead of let through. The console labels these refusals "WAF: request built to evade the rules". This protection cannot be switched off per website.
  • A single client that makes the firewall work unusually hard is now limited on your website, whatever it sends. Until now this applied only to large uploads. Your other visitors carry on.
8 November 2026Connections that never speak HTTPS are now cut at the network edge, blocked attackers can no longer hide behind another website's name, and forms sent from other sites can no longer act with your visitors' sessions.

Breakwave

  • Connections that open but send junk instead of a secure HTTPS start are now cut at the network edge, and the sender is shut out of every website for a while.
  • Visitors who use tools to get around internet censorship are not mistaken for attackers: their connections work as before.
  • Fixed: visitors using some of these tools could wait a few seconds and then fail to connect. They now connect at once.
  • A blocked attacker can no longer get around the network edge's blocks by connecting under the name of another website.
  • Some security scanners that test your website's encryption are no longer shut out for a while after a single test.

Website protection

  • Forms sent to your website from another site reach your server as they were sent. A payment provider's return still works, but a form on another site can no longer act with your visitor's logged-in session.
  • A single client that keeps a very large number of requests waiting on your server is now stopped on your website, instead of new requests to your whole website being refused. Your other visitors carry on.
  • Redirect rules that keep the path can no longer send visitors to another domain.
  • Third-party uptime checkers are trusted within a fair limit, since anyone can point them at any website. Your own monitors keep working.

Account

  • Password resets now ask for the same quick verification as sign-in.
  • Adding a domain or subdomain that is, or was, on another Shieldify account now needs a TXT record that proves the domain is yours. Your own domains and new domains are not affected.
2 November 2026Shieldify's check is harder to pass without a real browser, and attacks that try to wear out our network edge get much less out of it.

Bot protection

  • Shieldify's browser check now asks for more of the browser's own work, which makes it harder for tools that only imitate a browser.
  • An address that keeps collecting new passes for your website has to do a little more work for each one. Nobody is refused for this; people sharing an address may wait a moment longer.
  • A check or CAPTCHA page left open while we update reloads by itself instead of failing.

Breakwave

  • Forged packets made to look like a visitor's connection no longer count against your website or its visitors.
  • Attack traffic sent in fragmented packets is now stopped at the network edge.
  • Clients that are already stopped are cut off before the encrypted connection is set up, so they cost our servers almost nothing.

During large attacks

  • Floods of connections that are opened and then left idle can no longer keep new visitors out: when room is needed, idle connections are closed first.
  • A single website under attack can no longer use up the connections the network edge needs for every other website.
  • Large files are now limited while they are being cached, so a flood of large downloads cannot fill the cache.
  • Our network edge keeps memory in reserve during a flood and frees it from idle connections first.
31 October 2026Bots that pretend to be a browser are stopped much sooner, and large attacks cost our servers much less.

Bot protection

  • Attack tools that disguise themselves as a well-known browser are now told apart from the real browser and stopped at the network edge.
  • Floods that imitate browsers are stopped at the network edge much sooner: an attacking address gets very few requests through before it is shut out of your website.
  • Bots that keep coming back to Shieldify's check without ever completing it are stopped sooner. A real browser that is still on the check, reloading or opening new tabs, is never stopped this way.

During large attacks

  • Shieldify's check and CAPTCHA pages are now prepared ahead of time, so a flood of requests for them costs a fraction of what it did.
  • Our network edge and servers do less work for each attacking connection, which leaves more room for your visitors during a flood.
30 October 2026Who attacks your website, what Breakwave stopped of each attacker, and everything Shieldify knows about an address in one place.

Breakwave

  • A new Attackers list on the Breakwave tab shows the addresses Breakwave shut out of your website in the last 24 hours or 7 days: where each one comes from, how many of its connections and packets were stopped, and whether it is shut out right now. Open one to see its details, lift its ban, or block it for good with one click.
  • Click a country or network under "Where attacks come from" to see its attackers.
  • The chart now shows connection attempts and new attackers as well as attack traffic, and the tab counts the new attackers of the last 24 hours.

Traffic and Security events

  • Open a request to see the details of its IP address: its country and network, its requests to your website in the last 24 hours and what happened to them, the pages it asked for most, whether it is stopped right now, and what Breakwave stopped of it at the network edge, which never shows up in your traffic.

Firewall

  • A tool that keeps probing your website for weaknesses and is blocked by the firewall again and again is now stopped on your website for a while, so it stops keeping your server busy. A browser that passed Shieldify's check is never stopped this way.

Bot protection

  • On a shared network, such as an office or a mobile operator, people whose browser passed Shieldify's check keep reaching your website while a bot on the same network is stopped.
  • Bots that keep connecting to your website over https:// without ever getting past Shieldify's check are now stopped at the network edge, also when each address sends only a little. A browser that is still on the check is never stopped this way.

Plain HTTP

  • Visitors who open your website with http:// are sent to https:// by the network edge itself in most cases, before anything reaches our web servers. These redirects still count in your traffic and bandwidth.
  • Tools that attack your website over http:// are now recognized and stopped one by one, as over https://: a tool is stopped at the network edge on your website only, not every device behind its address. A client that keeps ignoring the redirect to https:// is stopped.
  • In the attack report, redirects to https:// are no longer counted as "Passed to the website".
29 October 2026References for your own rules and for server errors, redirects that keep the path, and large downloads shared fairly.

Rules

  • When one of your custom rules, rate limits or the "Block AI crawlers" setting blocks a request, the page now shows a reference too. Paste it into Security events: it names the rule that stopped the request and links to it.
  • A redirect rule can now keep the path: send /blog/post to the same page on your new domain, or move a section so that /old/page goes to /new/page.

Origin

  • When your server doesn't answer, the error page your visitors see carries a reference as well. Paste it into Security events to see when it happened and why your server didn't answer.

Downloads

  • Large downloads are now shared fairly. When many visitors download large files from a website at the same time, each of them gets an equal share and the downloads are slowed for a while, so that every website on the network stays fast. Pages and small files are not affected, and downloads keep going.
  • A device that floods a website with downloads is stopped on that website for a while. Other people on the same network, such as an office or a school, keep downloading.
  • A new "Large Downloads" alert under Notifications tells you when your website's large downloads were slowed.
27 October 2026A reference on every page the firewall blocks, so you can find the request in seconds.

Firewall

  • When Shieldify's firewall blocks a request, the page now shows a reference such as LYNX-4821-0934-7710. Your visitor sends it to you: paste it into the search on the Security events tab to see what was blocked and why, and let that request through on that path with one click.
  • Apps and webhooks that show no page get the same reference in the Shieldify-Ref response header.
  • The search also finds older references, as far back as the firewall's logs go, and tells you when a digit was mistyped.
25 October 2026Certificates that no longer wait for names that do not point to Shieldify yet, and the reason when your server does not answer.

SSL

  • Shieldify now requests a certificate only for the names of your website that already point to Shieldify. A www without a DNS record no longer holds up the certificate for your main name; the www is added on its own once it points here.
  • Adding a name to a working certificate keeps the current one serving while the new one is issued, and a failure leaves it in place.
  • The SSL tab no longer lets you turn on SSL or Force HTTPS before your certificate exists, and it updates on its own when the certificate arrives.

Origin

  • When your server does not answer, the "not responding" banner, the Origin tab and the alert email now say why: the connection was refused, did not open in time, failed its HTTPS setup or certificate check, or closed without an answer. Each comes with what to check on your server.

Fixes

  • Fixed an issue where a certificate extended with a new name reached visitors only about a minute later.
24 October 2026Shieldify Research grows into a section of its own, with guides and a vulnerability watch.

Research

  • shieldify.ee/research/ now gathers our attack reports, vulnerability notes and guides, and is in the top menu of every page. New articles arrive in an Atom feed.
  • A second attack report: the 23 October HTTP/2 flood against a login page.
  • Vulnerability watch: what happened with php2shell, the two critical PHP flaws, and what to do now.
  • Four guides: what a Layer 7 DDoS attack is, the first 15 minutes under attack, how a website's origin address leaks, and why blocking countries, networks and addresses fails.

Fixes

  • Fixed an issue where a website our team set up for you could go offline again, and retry its setup every 15 minutes, when its certificate could not be issued yet.
23 October 2026A public status page, and much less work for each request during HTTP/2 floods.

Status Page

  • status.shieldify.ee shows whether the Shieldify website, the console, its API and our DNS are up right now, with their recent history.
  • Every page of shieldify.ee shows the live status in its footer, and on larger screens in the bar at the top.

DDoS Protection

  • Shieldify's web server now handles each request of an HTTP/2 flood with less than half the work it took before, in our tests with the shape of the 20 October flood. More room is left for every website during an attack.

Console

  • The console now restarts its own service if it ever stops answering, and records what held it up so we can fix the cause.
  • The console runs on the current versions of all of its software.
  • Fixed an issue where, on 23 October from 10:13 to 18:36 UTC, the Requests tab showed an error and attack waves stayed open, so their end alerts were not sent. The waves closed once it was fixed.
22 October 2026Our first research report, documentation for every part of the panel, and custom rules that save again.

Research

  • Shieldify Research publishes what we measure in real attacks. The first report, at shieldify.ee/research/, takes apart the 20 October HTTP/2 flood: its size, its sources and its shape, and what it means for defenders.

Documentation

  • The docs now cover every part of the panel: the reporting pages, DDoS settings, the firewall, custom rules, rate limits, Breakwave, Zero Trust, caching, origin settings, billing, account security and troubleshooting.
  • The setup guide now points your root domain with a CNAME record first, and with an A record only where your DNS provider takes no CNAME there.
  • A redirect loop after setup now has its own troubleshooting entry: point Shieldify at your origin over HTTPS on port 443, or turn off the server's own redirect to HTTPS.

Custom Rules

  • Fixed an issue where the console refused to save a rule or an exception that names attack paths such as /.env or /.git, taking the rule itself for an attack.
21 October 2026New pricing from €4.90 a month, protection against two critical PHP flaws, and more headroom for every website during the largest floods.

Pricing

  • Shieldify now starts at €4.90 a month, tax included. One subscription covers every website on your account: your first domain with up to 10 subdomains, and 1 million requests a month for the whole account. Each further domain adds €1 a month.
  • Past the quota, each further million requests costs €1, counted to the request. Requests Shieldify blocks are never counted, and nothing is counted while a website is under attack.
  • The new Billing page in the panel shows this month's requests, what they come to, and your domains. Set a monthly limit there: we email you at 50%, 80% and 100% of it, and at the limit requests past the quota are no longer charged. Your websites stay protected.
  • Every customer keeps every protection. There are no tiers.
  • Already paying €19.90 for a website? Its subscription keeps running as it is. The Billing page shows how to move the website to your account's subscription when you want to.

DDoS Protection

  • When Shieldify cuts off a client during an attack, it now also closes the client's connection at once. Requests the client had already sent on it are dropped without being processed, and each still counts as stopped in your attack waves.
  • While a website is under attack, Shieldify limits how many requests each new connection to it can have open at once. Most of what a flood piles up is refused before Shieldify reads it; a browser simply sends its other requests a moment later.
  • In our tests with the shape of the 20 October flood, the two halve the work Shieldify does for each attacking connection, leaving more room for every website during an attack.
  • Breakwave, which stops floods before they reach our web server, now recognises more of the traffic that attack tools send.

Firewall

  • On 21 October Shieldify's WAF started blocking attacks on two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, hours before PHP published its fix. More protection for the same flaws followed that night.
  • Both are on for every website and can be switched off per website under Shieldify Emergency Signatures. Update PHP as well: these rules buy you time, they do not replace the fix.

Browser Check

  • Some in-app browsers on iPhone, such as Quark's, bring their own browser engine. They are no longer taken for a tool and asked to solve a CAPTCHA.

Fixes

  • Fixed an issue where a paused website could still pass a visitor on to its origin after the visitor solved a browser check. A paused website now shows its paused page to everyone.
  • Fixed an issue where sign-up accepted an email address that mail servers refuse, so the sign-in code never arrived.
  • Fixed an issue where a request from an address you always allow could skip Zero Trust when one of your custom rules asked for a check. Such requests now meet Zero Trust like any other, and count as clean requests.
20 October 2026Bot checks that are much harder to get around, Shieldify's own CAPTCHA, and a simpler way to add a website.

Browser Check

  • Every check page now gives the browser its own small task that only a real browser can do. A script that never runs a browser can no longer answer it.
  • A pass is tied to the browser that earned it. It cannot be reused anywhere else.
  • A pass used far more than a person ever could is withdrawn, and the client solves a CAPTCHA to go on.
  • During attacks Shieldify looks closely at every client, and one that does not look like a real browser solves a CAPTCHA first. A real browser with an unusual setup is never blocked: at most it sees the CAPTCHA.
  • Browsers driven by automation tools are now recognised even when they try to hide it, and are sent to the CAPTCHA.

Shieldify's Own CAPTCHA

  • Shieldify's own CAPTCHA replaces the previous CAPTCHA service. The visitor ticks "I'm a person", then the browser does a short piece of work: usually under a second on a computer, a second or two on a phone.
  • During attacks the work grows, so every pass costs an attacker more.
  • It is checked by Shieldify itself, with no outside service to slow it down or run out of capacity.
  • The same checkbox now protects the Zero Trust email form on your website and the console's sign-in, sign-up and Startups application forms.

Adding a Website

  • The new website wizard asks for your domain, your server and your protection settings first, then the trial or subscription; the DNS change comes last. Your website keeps working until you change DNS, and Shieldify adds it as soon as the domain points to Shieldify.
  • A setup you leave halfway, for example to pay, continues where you left it.
  • The wizard's last step shows the WAF switch; permanent mitigation and the two thresholds are under "Advanced settings".
  • "Start Free Trial" on shieldify.ee now opens sign-up.

Your Account

  • You sign up and sign in with your email address; there is no separate username. A password needs at least 8 characters with an upper-case and a lower-case letter; a symbol is no longer required.

Console

  • The Analytics tab is redesigned: the tiles (visitors, page views, requests, bandwidth) choose what the chart shows, cached and bot requests sit beside them, and four cards show pages and referrers, countries, browsers and devices, and responses by status, including how often your server did not answer.
  • Page views no longer count files that browsers check in the background, such as the web app manifest.
  • The Caching tab lists your rules first, with one-click common rules. Development mode is a switch, and purges ask before they run.
  • Zero Trust explains itself in three steps. Each protected path is a row with its own switch, and every change is saved and applied at once.
  • Breakwave's chart shows its scale and the details on hover. Blocking a country or network asks first and shows its share of your traffic; private mode is a switch.
  • A paused website's page now tells its visitors that the website is unavailable for now.
  • Certificates that could not be issued are retried automatically. The "Retry SSL" button is gone: the Certificate card shows the certificate's state and, when it is waiting, the next attempt.
  • The request list on the Traffic tab shows the right number of pages; it no longer offered pages that turned out empty.
19 October 2026See who is behind every attack wave.

Attack Waves

  • Each attack wave now shows who sent it: how many addresses and networks took part, how the wave grew minute by minute, the countries and networks it came from, the browsers the requests claimed to be, the protocols, pages and referrers they used, what Shieldify did with them, and the busiest addresses. Available for attacks from 19 October on.
  • Every reason for automatic mitigation now has a readable name in the console.

Shared Networks

  • When one device on a shared address, such as a mobile network or an office, has to solve a CAPTCHA, the other devices on that address are no longer asked.

Notifications

  • Attack alerts are no longer posted to Discord two or three times when Discord answers slowly.
  • "Server not responding" alerts now go by e-mail only.
18 October 2026We built our own web server, designed for attacks, and every website Shieldify protects now runs on it. There is nothing you need to do.

Our Own Web Server

  • On 18 October 2026 at 17:05 UTC we moved every website Shieldify protects to our own web server: the software that receives every request, checks it, and passes the good ones on to your server. It is built around one question: what happens when an attack lands.
  • Every website switched over at once, and nobody had to change a setting, a DNS record or a certificate.

During Attacks

  • Turning away an attacking request now takes about a quarter of the CPU it took before, and that cost stays flat as more cores join in. The same machine can absorb several times more attack traffic before it gets busy.
  • Requests that reach your website cost about a third of the work they used to.

Firewall

  • The firewall inspects each request with about a fifth less CPU, which gives it about a quarter more room.
  • It runs separately from the rest of the server: if the inspection engine ever fails on a request, it restarts within a moment and your website keeps serving.

Updates

  • Updates no longer drop connections. When we deploy a new version, new visitors wait a fraction of a second instead of being turned away. In our tests, dozens of restarts under load refused no requests at all.
  • After a full machine reboot, everything was serving again 17 seconds after the system started.

Custom Rules

  • Custom rules are checked when you save them. A rule the server cannot apply is refused with a clear message, instead of being saved and doing nothing.
  • Blocks that Breakwave applies at the network front line now count toward your rule's 24-hour hits too.
16 October 2026Analytics and Caching in the console, alerts when your server stops answering, and Shieldify now stops clients your website keeps refusing.

Analytics

  • A new Analytics tab shows your visitors over the last 24 hours, 7 days or 30 days: page views, the most visited pages, referring websites, countries, browsers, operating systems, devices and status codes.
  • It counts the requests that reached your website, from Shieldify's own records, so there is no script to add. Bots are counted apart; requests Shieldify stopped stay on the Dashboard and in Security events.
  • Visitors are unique addresses, an estimate.

Caching

  • A new Caching tab. Cache rules cache pages by path for a minute, 10 minutes, an hour or a day, or as long as your website's own headers allow. "Never cache" keeps a path out of the cache, static files included. The first matching rule applies.
  • A page is never cached for a visitor who has a cookie from your website, such as a signed-in visitor, nor when your website marks it private or no-store, or sets a cookie. Static files are cached as before, without a rule.
  • Purge everything, or only the URLs you list.
  • Development mode bypasses the cache for 3 hours while you work on your website.
  • The tab shows how much was served from the cache in the last 24 hours.

Website Server

  • When your website's server stops answering, you get an e-mail (and a Discord message, if set up) and the dashboard shows a notice; you hear again when it answers. Shieldify sees this in the requests themselves and never probes your server. Turn it off under Notifications.
  • Visitors get a clearer page: it shows that their browser and Shieldify work and your server does not answer, and it tries again by itself every 30 seconds.
  • Pages cached by a rule are still served while your server does not answer.

Refused Requests

  • When your website keeps refusing a client's form or API requests (an error such as 400 or 403), Shieldify stops that client's requests to that address for a short while. The rest of your website stays open to it; a client that keeps going is blocked on the website.
  • Pages not found (404), your website's own rate limiting (429) and clients your website also answers successfully are never counted.
  • When your website refuses most of its requests within an hour, you get an e-mail (and a Discord message, if set up) with the addresses involved, at most once a day, and the dashboard shows a notice.

Automated Browsers and Shared Defense

  • Automated browsers solve a CAPTCHA before they open pages or send forms.
  • A client stopped on another website protected by Shieldify solves a CAPTCHA before it opens pages or sends forms on yours.

DDoS Settings

  • Strict Mode: Automatic, Off or Always on.
  • Verification during attacks: Automatic (a short browser check, a CAPTCHA when the attack gets heavy) or a CAPTCHA for every new visitor.
  • Sensitivity: Low, Normal or High, for how readily automatic mitigation turns on. Low suits websites with large legitimate peaks.
  • Each new protection above has its own switch.

Custom Rules and Rate Limits

  • New action "Skip browser checks" for app and webhook paths, such as mobile apps and payment callbacks: no browser check or CAPTCHA, while rate limits, bans and your other rules keep protecting them. A ready template is included.
  • New condition "Under attack", for rules that apply only while mitigation is on, or only while it is off.
  • "Add sign-in protection" limits sign-in, sign-up and password reset attempts per visitor in one click.

Attacks

  • Attack waves start from 1,000 stopped requests, so the list and the alerts show real attacks.
  • Each attack shows its details: the paths, the reasons, the busiest addresses, and the countries and networks behind it.
  • The dashboard shows "Mitigation is on" while Shieldify is mitigating.
  • During an attack the traffic log lists every request that reaches your website and a sample of the stopped ones, with their reasons.

Weekly Report

  • Includes Strict Mode periods and the form or API requests your website refused.
15 October 2026Introducing Strict Mode: bots posing as browsers get a CAPTCHA, your visitors go straight through.

Strict Mode

  • Shieldify spots bots that pose as ordinary browsers.
  • When much of a website's traffic comes from such bots, the website switches to Strict Mode by itself. They get a CAPTCHA; real visitors go straight through, and anyone with an unusual setup can solve the CAPTCHA and carry on.
  • Strict Mode ends by itself when that traffic stops. The website's page in the panel shows when it is on and when it was on in the last 7 days.
  • On every website, with nothing to set up.

Traffic

  • A new Reason column shows why Shieldify answered a request itself: the browser check, a CAPTCHA, a firewall rule, a rate limit or a ban.
  • Shieldify's own files, such as the check page's style and the CAPTCHA, no longer appear in your traffic.

Forms and Payments

  • When a payment provider or a bank's 3-D Secure page sends your customer back to your website with a form, the return reaches your website with all of its data, also during an attack.
  • A form sent while the browser check or a CAPTCHA is on screen is sent on automatically once it is passed. Browsers without JavaScript get a Continue button.

Firewall

  • Requests with a text/plain body, such as analytics beacons (PostHog, navigator.sendBeacon), are accepted and inspected like JSON.

During Attacks

  • Visitors who have your single-page app open (Next.js, React and the like) are never shut out when the website goes into attack mode: reloading the page brings the browser check, as for any visitor.
  • On shared addresses such as mobile networks and offices, Shieldify's limits count each device on its own, so many visitors behind one address do not add up to a limit.
  • The attack's own requests can no longer use up the room real visitors need to pass the browser check or the CAPTCHA.
  • When the CAPTCHA service is busy, the page sends the same answer again a moment later instead of asking for a new CAPTCHA.
  • Certificate renewals keep working while a website is under attack.

Panel

  • Deleting a website also deletes all of its records, such as bandwidth, firewall settings history and Breakwave statistics.
14 October 2026Firewall exceptions now live in your custom rules.

Custom rules

  • A "Skip firewall" rule can skip only some firewall rules: enter their rule numbers (for example 942100) and every other rule still inspects the request. Without rule numbers it skips the whole firewall, as before.
  • "Skip on this path" in Security events adds such a rule for the path, or adds the path to the rule that already skips that firewall rule. Path exceptions you had before were moved into custom rules for you.
  • Skip rules now work wherever they are in the list, also below an Allow rule.
12 October 2026Introducing Pinpoint Bans: block the attacker, not the whole network.

Pinpoint Bans

  • On a mobile network, in an office or on a school Wi-Fi, many people share one internet address. Shieldify now stops only the device that attacks; everyone else on that address keeps browsing your website.
  • Shieldify tells devices apart by how they connect. The other visitors on the address are treated like any visitor: during an attack, they get the usual browser check.
  • Breakwave works the same way at the edge of our network: it turns away only the attacking device and closes the connection it was attacking through.
  • Busy shared addresses, such as mobile networks and offices, are recognised: one device's ban does not shut out the other people behind the same address.
  • An attacker that keeps trying to slip past its ban is still blocked.
  • On every website, with nothing to set up. Unban on the Breakwave page, trusted addresses and custom rules work as before.
10 October 2026A stronger firewall, much lighter answers to attacks and twice the capacity for secure connections.

Firewall

  • The firewall now inspects file uploads up to 32 MB, including every form field sent with them. Before, a form with a file over 1 MB passed without inspection.
  • Uploads over 32 MB are refused (413) unless you allow large request bodies for the website (Firewall > Large request bodies); then they pass without inspection. Other request bodies keep their 1 MB limit.
  • The firewall rules and engine are updated, which closes several known ways to get an attack past the rules.
  • API requests with PUT, PATCH and DELETE are no longer refused by the firewall. Their bodies and parameters are inspected like those of any other request.
  • The firewall is faster: about a third more requests per server core.
  • Custom rules on a path now also match its variants, such as /wp-login.php/ and /wp-login.php;x. Allow and Skip firewall rules, and redirects, still match only the path as written.

During Attacks

  • Shieldify answers attack traffic with much less data: the check and CAPTCHA pages are about half their former size, and their style and logo come from a cached file. Attacks use less of the network, leaving more room for your visitors.
  • Attack tools that keep asking for check pages are slowed down and held, so they send far fewer requests. Addresses that keep doing it are shut out of the website by Breakwave.
  • Breakwave recognises more attack tools at the edge of our network.
  • The browser check no longer runs short of room during very large attacks, so real visitors are not shown a temporary error page.
  • During an attack, the request log keeps every request that reached your website and a 1 % sample of the refused ones, so the log stays readable.

Faster Secure Connections

  • Shieldify now uses a new TLS engine that handles about twice as many new HTTPS connections per second on the same servers, which leaves more room during connection floods. Your certificates and settings stay as they are; there is nothing to do.

Panel

  • If the Firewall tab cannot load your settings, it now says so instead of showing an empty list that a save could have cleared.
  • A tidier top bar: the breadcrumb is gone, and the menu button shows only on phones.

Maintenance

  • Security updates for the edge servers, and their software rebuilt with additional hardening.
7 October 2026A new network for the Shieldify edge, a free program, new settings for your websites and a round of protection and panel improvements.

New Network and Addresses

  • Shieldify now runs on a new network in France with always-on DDoS mitigation in front of it. Websites that point to shield.shieldify.ee with a CNAME moved automatically. If you use an A record, point it to 5.135.245.163 (a CNAME is recommended).
  • The address 51.77.219.75, used for a few hours on 7 October, no longer serves websites. If an A record still points to it, change it to 5.135.245.163.
  • Connections from Shieldify to your server now come from 54.36.197.65, and during attacks also from 34.163.209.251 and 34.163.19.4. Allow all three in your server's firewall and in tools that block addresses automatically (fail2ban, CSF, Plesk, your provider's DDoS filter). The old address 80.91.71.190 is retired: remove it from your allowlists.
  • Shieldify must receive your visitors directly. Another proxy or CDN in front of Shieldify is not supported; with Cloudflare DNS, set the record to DNS only.

Shieldify for Startups

  • Shieldify is now free for startups, schools and universities, clinics and hospitals, and nonprofits. Apply at lynx.shieldify.ee/startups. Every application is read by our team; please write it yourself, as applications written with AI tools are not accepted.

Adding a Website

  • Point your DNS to Shieldify first, then add the website in the panel. The panel now checks that the domain points to Shieldify before it adds it. Do both steps in one sitting, ideally with a short TTL on the record.

New Settings

  • Large request bodies (under Firewall): the firewall now inspects request bodies up to 1 MB (was 128 KB). Bodies over 1 MB that are not file uploads are refused unless you allow them; allowed ones pass without inspection. File uploads are not affected.
  • Verify your server's certificate (under Origin, for https origins): when it is on, Shieldify only connects to your server if its certificate is valid for the name you choose.
  • Websites using the Nextcloud application profile can now use WebDAV for file sync. Add an Allow URI rule for /remote.php/ so sync clients are not asked to verify.

Faster and More Reliable

  • Responses are now buffered at the edge, so slow visitors no longer keep your server busy. Requests time out after 5 minutes; WebSocket connections stay open for up to an hour. For a streaming response, send X-Accel-Buffering: no.
  • Build files from Next.js (/_next/static/) and Astro (/_astro/) are now served from the Shieldify cache also to visitors who carry cookies, when your server marks them public or immutable.
  • A paused website now answers search engines with "come back later" (503) instead of a normal page, so your pages keep their place in search results.
  • When a website's own server stops answering connections from one of our addresses, only that website is moved to another address.

Stronger Protection

  • Blocked paths and rate limits now also match variants such as /Admin, /admin/ and /admin;x. Custom rules on a query parameter check every value it is given.
  • Tighter handling of unusual requests, connection upgrades and rewritten paths, so they can no longer slip past your rules.
  • Your server now receives the visitor's address only in X-Real-IP and X-Forwarded-For. CF-Connecting-IP and X-Client-IP sent by visitors are removed.
  • Bots that try to get around the check during an attack are now banned like any other attacker.
  • Breakwave now notices a flood of new connections to your website earlier and turns on stronger protection before the requests arrive, and it stops more attack tools before they reach your website.

Account and Panel

  • Signing in works again right after a mistyped password, without reloading the page.
  • After a password reset by e-mail, your passkeys are removed and you are told by e-mail; add them again under Profile.
  • Repeated failed sign-ins lock that account for a while. Passkey sign-in is not affected.
  • Times in the panel are shown in your own time zone.
  • Clearer error pages, and a "Could not load" message with a retry button instead of empty lists when data cannot be loaded.
  • If a payment was not completed, you can start a new checkout right away.
6 October 2026Introducing Shieldify Breakwave, a new front line for your websites.

Shieldify Breakwave

  • Once an attacker is caught, Breakwave turns it away at the very edge of our network, before it reaches any other layer of protection, so your website keeps more room for real visitors. Find it under Protect > Breakwave.
  • Smart bans: attackers are shut out of the website they attacked, and only that one. Someone else's attack never locks out your visitors. You can unban an address with one click.
  • Your blocks, instantly: blocks by address, country or network from your custom rules are applied at the edge.
  • See where attacks come from (countries and networks) and block one with a click. Charts cover the last 24 hours, 7 days or 30 days.
  • Trusted addresses (up to 50) are never shut out by Breakwave.
  • Private mode: allow only the addresses you list to reach your website, for example while it is under construction.
  • Your website's dashboard shows how much Breakwave stopped in the last 24 hours.

Notifications

  • New e-mail and Discord alerts. Attack alerts lead with what Breakwave stopped and how many attackers were shut out. They contain no addresses, countries or networks, so you can share them safely.
5 October 2026New protection tools since our 4 October 2026 update.

Custom Rules and Rate Limits

  • New Custom rules: block, challenge, ask for a CAPTCHA, allow or redirect requests. A rule can also skip the firewall for one path, such as a payment webhook, or only count matches so you can try it before it acts. Find them under Protect > Custom rules.
  • Rules can match the path, the query string or a single query parameter, method, user agent, headers, cookies, host, referer, content type, client IP or IP range (IPv4 and IPv6), the visitor’s country or network (AS number), request size, and whether the client is a verified search engine. Conditions include value lists (“is one of”, “contains any of”), “exists” and “is larger than”. A rule takes up to five conditions, a website up to 50 rules, and changes apply within a second.
  • Country and network rules: allow, check or block visitors by country, for example only the countries you serve, or by network, for example traffic from cloud and hosting providers where most bots run. Find a network by its name or AS number. Verified search engines can be kept out of the rule so your pages stay in search results. Country and network data: IP Geolocation by DB-IP, updated monthly.
  • Start from templates: WordPress hardening, sensitive files (.env, .git, backups), vulnerability scanners, fake search engines, selected countries only, cloud and hosting networks, and requests without a user agent. Every rule shows how often it matched in the last 24 hours, and a rule can switch itself off after an hour, a day, a week or a month.
  • New Rate limits for single pages: for example, at most 10 login attempts per minute from one visitor. Above the limit the visitor is asked to verify or to solve a CAPTCHA, or is blocked for the rest of the window. Each limit shows how often it was reached in the last 24 hours. Find them under Protect > Rate limits.
  • Block AI crawlers with one switch. GPTBot, ChatGPT, ClaudeBot, CCBot, PerplexityBot, Bytespider, Amazonbot, Meta and other AI crawlers are refused. Search engines such as Google and Bing are not affected.

Fewer False Positives

  • Skip a firewall rule on one page only: open the event under Security events and choose “Skip on this path”. The rule keeps protecting the rest of the website. Your exceptions are listed under Firewall rules, where you can remove them.

Reports and History

  • A weekly security report by e-mail every Monday. It covers requests, mitigated traffic, verification checks and attacks of the past week for each of your websites. You can turn it off per website under Notifications. The first report arrives on 12 October.
  • Traffic history is now kept for a full year, and the dashboard has a 1-year view.
4 October 2026Improvements since our 1 October 2026 update.

Smarter Web Application Firewall

  • The firewall now inspects JSON and XML request bodies. APIs, mobile apps and modern websites that send JSON or XML now get the same protection against SQL injection, cross-site scripting and other exploits as regular forms. Large or unusual JSON is never rejected because of its size.
  • Request bodies up to 128 KB are now inspected, so attacks hidden inside long form or API submissions are caught.
  • New application profiles for WordPress, XenForo, phpBB, Drupal, Nextcloud, phpMyAdmin, cPanel and DokuWiki reduce false positives on their admin and editor pages. Turn on the ones your website uses under Firewall > Applications. Each one relaxes only the checks its own application is known to trip, and only on that application's pages.
  • The protection profile you choose (Low, Medium or High) is now applied exactly as selected. All websites now use Low, the new recommended default with the fewest false positives. Choose Medium or High for stricter checks.
  • Fixed an issue where, after certain account changes, the firewall on some websites ran with an incomplete rule set.

Changes Apply Instantly

  • Changes you make in the panel now take effect within a second, without interrupting any website. This includes protection and firewall settings, rate limits, allow lists, private page rules and Force HTTPS.
  • Adding a website, issuing its SSL certificate, changing its origin server, turning on the www address and pausing or resuming a website are now instant as well.
  • Long-lived connections such as WebSockets, live dashboards and large downloads are no longer cut off when settings change, on your website or anyone else's.
  • Renewed SSL certificates are picked up without interrupting any website.

Stronger Protection During Attacks

  • Large uploads and form submissions now have fair rate limits per visitor and per website, so heavy requests cannot slow protection down for everyone. Normal use stays far below these limits.
  • During an attack, the background requests a page makes no longer push real visitors to the harder CAPTCHA.
  • Bots can no longer request verification pages without limit. Switching browser identity on every request no longer gets around the limits.
  • Pages with many images, scripts and styles now load completely on a visitor's first visit.
  • "Attack ended" alerts now arrive on time even on websites with very little traffic.
  • Closed a gap that let some requests skip protection checks.
  • Private page rules now also match addresses written with backslashes, as used by Windows servers.

Uptime Monitoring and Search Engines

  • Uptime checks from check-host.net are now recognized and no longer blocked, so your monitors show the real status of your website.
  • Only genuine search engine crawlers skip verification. Tools that fetch a page on a person's request are now checked like any other visitor.

New Panel

  • The panel has a completely new design. Each website's settings are now grouped into Website, Protect and Configure.
  • The traffic dashboard now offers Live, 1 hour, 24 hours and 7, 30, 90 and 180 days, and shows total traffic usage again. Rising normal traffic no longer looks like an attack on the chart.
  • Moving between pages shows progress right away.
  • Long operations, such as turning on the www address, no longer appear to fail while they finish.
  • The verification, error and CAPTCHA pages shown to your visitors now match the new design.

Trial and Billing

  • The free trial is now 7 days, and each domain can use the trial once. If a domain has already used its trial, the setup wizard tells you at the domain step.
  • Fixed an issue that could pause a paid website at renewal while the invoice was still being prepared.
  • You now receive an email 24 hours before a website's access period ends.
  • Paying for a paused website turns it back on automatically.

Reliability

  • Panel services now restart automatically after an unexpected failure, and server health is monitored around the clock.
  • Account and website settings are now backed up every night.
  • Our edge servers now use less than half the memory they did, which leaves more room for traffic spikes, attacks and many more websites.
  • Discord alerts now show the new Shieldify icon.

Shieldify Website

  • New pages explain DDoS protection, bot protection, the web application firewall and pricing, and include a step-by-step setup guide.
  • www.shieldify.ee now opens the website.
1 October 2026Improvements since our 27 September 2026 update.

Faster Websites

  • Pages served through Shieldify now load noticeably faster: Shieldify keeps its connections to your server open and reuses them instead of opening a new connection for every request.
  • Pages, stylesheets and scripts are now compressed on the way to your visitors, so they download faster.
  • Your server now receives far fewer new connections from Shieldify, which lowers its load during busy periods.
  • If your server cannot be reached, visitors now see an error page after 15 seconds instead of waiting up to a minute.

Smoother Visitor Verification

  • Fixed an issue where a form submitted after a few minutes on a website (for example sign-in, registration, checkout or comments) could be lost, requiring visitors to submit it again.
  • Many visitors and browsers sharing one network, such as an office, school or mobile carrier, can now complete verification at the same time.
  • Visitors who open many pages quickly are no longer mistakenly blocked for a short time.
  • The CAPTCHA now recovers from brief connection problems and returns visitors to the exact page they were on.
  • Forms sent to the HTTP address of a website with Force SSL now keep their content when redirected to HTTPS.
  • Visitors who reach a website while its setup is still completing can now pass verification instead of seeing the check repeatedly.

Search Engines

  • Major search engine crawlers such as Googlebot and Bingbot are now recognized reliably and are not asked to verify, protecting your search visibility. Bots that only pretend to be search engines are still checked.
  • The list of official search engine addresses is now refreshed automatically every week.

Stronger Protection During Attacks

  • Improved the stability and speed of protection during very large attacks.
  • Attacks from very large numbers of addresses are now blocked more completely.
  • A single attacker can no longer use up verification capacity and keep real visitors from verifying.
  • SSL certificates can now be issued and renewed even while a website is under attack.
  • Strengthened network-level DDoS protection in front of Shieldify.
  • Added automatic monitoring of the services behind visitor verification, so problems are detected and resolved faster.

Private Pages

  • Private page rules now match addresses more reliably, including variations in letter case and trailing slashes.
  • Improved the security of the private page access request page shown on your website.

Account and Panel Security

  • You can now sign in with a passkey, such as Face ID, Touch ID, Windows Hello or a security key. Add one from your Profile; password sign-in remains available.
  • Two-factor authentication codes can now be used only once.
  • Limited how many verification emails can be sent to an account, protecting inboxes from email flooding.
  • The panel can no longer be embedded in other websites, protecting against click-tricking attacks.
  • Website server addresses are now validated more strictly.

Safer Website Settings

  • A settings change that cannot be applied is now rolled back automatically, without affecting your other settings or websites.
  • Protection settings such as rate limits now have clear allowed ranges.
  • Deleting a website now also removes its SSL certificate.
  • Panel tools such as log search, DNS checks, cache purge and notification tests now have fair-use limits, keeping the panel fast for everyone.

Payments

  • Prices and checkout load more reliably, with a retry option when a connection is slow.

Refreshed Look

  • New Shieldify logo and color palette across the website, the panel and the verification pages shown to your visitors.

More Secure HTTPS

  • HTTPS connections now follow current security recommendations, and outdated encryption methods are no longer accepted. Very old browsers and devices without modern encryption support may no longer be able to connect.
27 September 2026Improvements since our 10 August 2026 update.

Smoother Visitor Verification

  • Fixed issues that could leave visitors stuck on a verification screen, especially when opening several pages or tabs at once.
  • Visitors now have more time to complete advanced verification without unexpected restarts.
  • Expired or interrupted checks recover more smoothly, making it easier to continue browsing.

Fewer Unnecessary Checks

  • Improved protection for websites that normally receive very little traffic.
  • Normal increases in visitors are less likely to trigger extra verification.
  • Protection now better distinguishes ordinary traffic growth from suspicious activity.

More Reliable Website Protection

  • Improved protection stability during busy periods and unusual traffic.
  • Updated website security rules to cover more suspicious requests.
  • Website block rules and private-page access settings are applied more consistently.

More Accurate Traffic Information

  • Improved the accuracy of traffic counts and live website status.
  • Traffic information recovers more reliably after temporary interruptions.
  • Protection alerts are delivered more reliably.

Easier Trial and Subscription Setup

  • Fixed an issue that could require a second click to start checkout when switching between trial and paid options.
  • Improved checkout recovery after interrupted attempts.
  • Made purchase assignment more reliable when connecting a plan to a website.

A Smoother Account Experience

  • Fixed intermittent errors when using the panel in several tabs.
  • Improved account verification and sign-in reliability.
  • Signed-in visitors now see their account details and a Panel shortcut on the Shieldify website, including mobile navigation.
  • Improved error messages for invalid settings and requests.

Safer Website Settings

  • Failed certificate renewals no longer remove an existing HTTPS setup or change your Force SSL preference.
  • SSL status messages now explain renewal problems more clearly.
  • Failed website connection changes restore the previous settings whenever possible, with clearer guidance when support is needed.
  • Improved validation of website connection settings.

Better Content Delivery

  • Improved static content caching while respecting private and personalized responses.
  • Fixed cases where the main domain and its www address could show incorrectly shared cached content.
10 August 2026

Better Availability During Very Large Attacks

  • Protected websites now stay fully available during exceptionally large, distributed attack waves involving many thousands of distinct sources, a scale that could previously put extra strain on the platform under extreme conditions.
  • Internal logging and monitoring during large attacks are now more efficient, so protection stays responsive and readable even at the highest observed traffic scale to date.

More Accurate Attack Wave Notifications

  • One ongoing attack is no longer reported as a stream of separate, repeated alerts; a sustained incident is now tracked and notified as a single event from start to finish.
  • Peak traffic numbers shown in attack notifications now better reflect the attack's sustained intensity instead of being skewed by a single brief traffic spike.

Increased Platform Resilience

  • Core protection processes now recover automatically from rare internal faults, reducing the chance that an isolated internal error could affect site availability.
  • Internal monitoring now detects these rare recovery events automatically, improving how quickly the operations team can respond.
22 June 2026

Shieldify Labs

  • Shieldify Labs is now part of the release validation flow for protection changes.
  • The lab checks realistic browser, API, verification, rate-limit, and origin behavior before changes are promoted.
  • This improves release confidence while keeping customer websites isolated from test traffic.

Protection and Notifications

  • Browser-like high-volume attack detection now responds earlier while keeping dedicated false-positive safeguards for clean human traffic.
  • Shieldify-owned lab validation can now split high-volume request tests across multiple local workers for more accurate edge-capacity measurements.
  • Shieldify-owned lab validation traffic is now reflected in live traffic metrics through the normal request path during approved edge-capacity tests.
  • Edge worker allocation now follows the full CPU capacity available on production nodes for higher L7 validation headroom.
  • High-volume protection profiling reduced internal shared-state contention in the L7 hot path, improving edge efficiency during approved Shieldify Labs capacity tests.
  • Live protection counters now use short internal batching during high-volume traffic so telemetry remains current without forcing every request to contend on the same shared state.
  • High-volume sensor observation now avoids unnecessary request parsing on lightweight skip passes while preserving detailed low-volume analysis.
  • Shieldify Labs profiling now reports per-phase L7 timing for approved capacity tests, helping isolate expensive protection stages faster.
  • Shieldify Labs can now isolate Engine challenge rendering during approved capacity validation, making it easier to measure verification overhead apart from origin throughput.
  • Enhanced mitigation has been tuned to avoid escalating on challenge volume alone when traffic appears diverse and healthy.
  • Trusted URI rules continue to support API-style bypass behavior while still contributing to protection visibility.
  • HTTPS redirect traffic is now observed before redirect handling, improving visibility into HTTP-side floods.
  • Manual URI block and allow wildcard rules now use stricter prefix-bound matching.
  • Verification infrastructure has additional edge-side throttling and caching for public verification assets.
  • Mitigation activation emails and Discord alerts are deduplicated more carefully to prevent duplicate notifications for the same incident.

Admin Operations

  • Admins can now update a user's email address and username from the Users area.
  • Account detail edits and password resets are now grouped into a clearer admin workflow.
19 June 2026

Dashboard and Traffic Visibility

  • The 30-day traffic chart now displays daily timeline labels instead of confusing time-of-day labels.
  • Monthly traffic views are now easier to read and load more efficiently on websites with larger histories.
  • Website traffic summaries remain aligned with the selected reporting period.

Website Management

  • Website SSL recovery tools are now available from the SSL area, making certificate troubleshooting easier to find.
  • Website deletion is now limited to admins to reduce the chance of accidental customer-side removal.
  • Website provisioning controls have been simplified so customers see fewer operational details.

Verification Reliability

  • Website verification settings are now applied more consistently across protected websites.
  • Verification behavior has been improved for customer websites that use protected paths or advanced verification.

Stability Improvements

  • Additional safeguards were added around invalid website host configuration.
  • Admin controls and website configuration flows now avoid more edge cases that could create confusing service warnings.
17 June 2026

Zero Trust Access

  • A new Zero Trust area is available for protecting private website paths.
  • Customers can add email-code access policies for sensitive paths such as admin panels, dashboards, staging areas, and internal tools.
  • Policy creation now uses a cleaner popup flow for adding or editing protected paths.
  • Access policies are managed individually, so each protected path can be active or paused on its own.
  • Email verification is now paired with an additional human check before an access code can be requested.
  • Access request screens no longer reveal whether an email address is allowed by a policy.
  • The Zero Trust interface has been simplified so customers focus on protected paths and policy status instead of global mode controls.
14 June 2026

Bandwidth Visibility

  • Website dashboards now show total traffic usage for the last 30 days.
  • Usage visibility includes both incoming and outgoing website traffic.
  • Live usage information has been added next to Traffic Health for quicker monitoring.
  • Application-level attack traffic that reaches the protected website is also included in usage visibility.
13 June 2026

Account Security Improvements

  • New registrations now require email verification before account access is completed.
  • Login protection has been improved for unusual sign-in activity.
  • If a login is detected from a new location, Shieldify can request an email verification code before allowing access.
  • Verification codes now have stricter safety limits to reduce abuse.
  • Password reset flows have been improved with clearer emails and a more polished reset experience.
  • Users can now enable authenticator app two-factor protection from the Profile page.
  • Authenticator setup supports both QR code scanning and manual setup codes.
  • When authenticator protection is enabled, sign-ins require an authenticator code after the password step.
  • Password changes for authenticator-protected accounts now require an authenticator code as an extra safety check.
  • For authenticator-protected accounts, unusual sign-in activity uses the authenticator app instead of email verification.

Email Notifications

  • Shieldify can now send important account, support, and protection notifications by email.
  • Support ticket updates can now reach users more reliably.
  • Attack start and end notifications can be delivered by email where enabled.
  • Website notification settings now include email controls and are easier to manage.

Better Traffic Visibility

  • Live traffic statistics are more accurate and less likely to show old data as current activity.
  • Traffic charts have been improved for websites with very low or no recent traffic.
  • Request counters and live views now recover more cleanly after configuration changes.
  • Admin traffic charts are easier to read and no longer show confusing axis values in some high-traffic cases.

Faster Request Log Experience

  • The Requests page has been optimized for websites with large traffic logs.
  • Searching request logs is now smoother and uses fewer resources.
  • Pagination now reports page counts more accurately.
  • Request classifications are displayed more clearly.

Website Access Management

  • The Access screen has been redesigned for clearer rule management.
  • Trusted IP and path rules are easier to add, review, and remove.
  • Unsafe broad allow rules are now rejected to help prevent accidental exposure.
  • Unsaved-change indicators are more accurate and no longer stay active when a rule list is returned to its original state.

SSL and Setup Flow Improvements

  • SSL controls now handle Force SSL more clearly.
  • SSL cannot be accidentally disabled while Force SSL is still active.
  • Website setup now supports custom origin ports for customers who do not use only the standard web ports.
  • Origin and SSL configuration feedback is clearer during setup and updates.

Admin and Website Management

  • Admins now have more control over whether members can create new websites.
  • Registrations can stay open while website creation remains admin-managed.
  • Admins can create websites on behalf of users from the admin panel.
  • User and website management screens have been refined for clearer daily operations.

Protection Reliability

  • Protection behavior has been tuned to better support legitimate high-volume customer traffic.
  • Trusted payment-related traffic handling has been improved.
  • Short-term abusive traffic handling is more controlled, helping reduce false positives while keeping active protection effective.