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

Shieldify Now Runs on AWS.

On 17 November 2026 our edge moved to AWS in Frankfurt. Visitors now reach it through AWS's global edge, protected by AWS Shield and announced from 130 points of presence in 53 countries, so network floods end there, near where they come from. Our own edge still makes every decision about the requests that pass, your visitors' data still stays in the EU, and the price is the same.

17 NovemberShieldify's edge moved to AWS in Frankfurt, Germany.
130 locationsin 53 countries announce our addresses; network floods end at the nearest one.
EU onlyTraffic is decrypted only on our server in Frankfurt; backups are encrypted in Stockholm.
Same priceNetwork protection is included for every website, and attacks are never billed.
Why we moved

A flood should end where it starts

Shieldify stops attacks at two levels. Floods made of requests, the Layer 7 attacks that look like real visitors, are our own work: our edge reads every request and decides. Floods made of packets, the network-layer (Layer 3 and 4) attacks that try to fill a link, have to be absorbed before they reach any server, however good that server is.

Until November that second job was done in the one data center where our server stood. Every flood travelled across the internet to that place, and what one site's network could take was the limit. We wanted the flood to end near its sources instead, spread over many places, before it gets anywhere near us or you.

How it works now

Anycast in front, our edge behind it

Visitors reach Shieldify through AWS's global edge. Our two addresses are announced from all of its 130 points of presence in 53 countries at once (anycast), so every connection, and every flood, arrives at the AWS location nearest to where it was sent from. AWS Shield protects those locations against network floods.

  • Only web traffic travels on. Everything that is not a visit to a website ends at AWS's edge and never reaches our server.
  • Visitors' connections cross AWS's own network to Frankfurt instead of the open internet.
  • Our edge decides the rest. Breakwave, the browser check, the firewall and your own rules run on our server in Frankfurt, as before. Your server still sees each visitor's real IP address.

The home page and the DDoS protection page show the network layer in more detail.

What stayed the same

Decrypted only in the EU, by us

  • Encryption ends in Frankfurt. AWS's edge locations pass visitors' encrypted traffic on without decrypting it; the TLS encryption is ended only on our server in Frankfurt, Germany.
  • Data stays in the EU. The server and its data are in AWS's Frankfurt region; the encrypted backups are in Stockholm, Sweden. The Trust Center lists every provider we use.
  • No CDN. Nobody but us decrypts or inspects your visitors' requests: the protection is our own software, on a server we run.
  • The price. One plan from €4.90 a month, every protection included, and attack traffic is never billed.
What you need to do

Usually nothing. Check two things.

  • Your DNS. A CNAME to shield.shieldify.ee follows on its own. A records must point to 15.197.200.140 and 99.83.142.152.
  • Your server's allow list. If your server or hosting firewall lets in only Shieldify, it must allow 63.189.207.48, the address our edge uses to reach your server. It is also the address to trust for the visitor's real IP. The setup guide has the details for nginx and Apache.

Not sure? Write to contact@shieldify.ee and a person will check it with you.

More research

Floods End Near Their Sources.Your Website Keeps Serving.

Put Shieldify in front of your website: one DNS change, from €4.90 a month.