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

Put Your Website Behind Shieldify.

From a new account to a protected website in about ten minutes: DNS, certificates, your server's firewall, real visitor IPs, APIs and alerts. Then a tour of every part of the panel.

Before you start

What you need

  • Access to your DNS at your registrar or DNS provider, so you can add or change one record.
  • Your server's address: the IP address or hostname where the website runs today. Shieldify calls this the origin.
  • About ten minutes, plus the time your DNS provider needs to publish the change.

Lower the TTL of the record you are going to change to a few minutes a day before you switch. The move to Shieldify, and back if you ever need to, then takes effect quickly.

Step 1

Create an account

Create an account and confirm your email address with the code we send. Then choose Add website. Add a passkey or an authenticator app to your account early (see Account security).

Step 2

Add your website

Nothing changes for your visitors yet: you point the DNS at the end, once everything is ready.

  1. Enter the domain, for example example.com. The panel checks that the domain exists and is not already protected.
  2. Enter the origin: the IP address or hostname of your server. The protocol and port are detected automatically. Choose www if www.example.com should be protected by the same website.
  3. Keep the protection settings: the defaults suit most websites, and you can change everything later.
  4. Start the 7-day trial: add a payment method in Stripe Checkout. Nothing is charged during the trial, and your account's subscription, from €4.90 a month, begins after 7 days unless you cancel. Each account and each domain can use the trial once. One subscription covers every website on your account: once it runs, a new website joins it and this step is skipped. See Billing and pricing.
Step 3

Point your DNS to Shieldify

The panel then shows the records to set at your DNS provider. Point the root domain (example.com without www) to shield.shieldify.ee with a CNAME record: it follows Shieldify's infrastructure automatically.

TypeCNAME
Name@
Targetshield.shieldify.ee

Cloudflare accepts a CNAME on the root domain (CNAME flattening), and some providers offer an ALIAS or ANAME record for the same.

Only if you cannot use a CNAME: set two A records to the addresses the panel shows (today 15.197.200.140 and 99.83.142.152). Set both: either one alone works, but two keep your website reachable if a path to one fails.

TypeA
Name@
Address15.197.200.140
TypeA
Name@
Address99.83.142.152

For www or any other subdomain, use a CNAME record:

TypeCNAME
Namewww
Targetshield.shieldify.ee

The panel checks the record every few seconds. As soon as it points to Shieldify, the website is created and protection switches on by itself; you can close the page meanwhile. Depending on the old record's TTL the change itself takes from a few minutes to a few hours to be seen.

Remove other A and AAAA records for the same name, or part of your visitors bypass Shieldify.

Visitors must reach Shieldify directly: another proxy or CDN in front of Shieldify is not supported. Using Cloudflare DNS? Set the record's proxy status to DNS only (grey cloud). With the orange cloud, traffic would stop at Cloudflare and never reach Shieldify.

If another account is setting up the same domain at the same time, the panel asks you for a TXT record to confirm the domain is yours; the website is created for the account that adds its own.

Step 4

Get the SSL certificate

A free Let's Encrypt certificate is requested as soon as the domain points to Shieldify, and renewed before it expires. Nothing else is needed. Under SSL and TLS you see its state, and you can switch on Force HTTPS so every visitor is moved to the secure address.

If a request fails, the panel shows the last error and Shieldify tries again by itself. The usual cause is DNS that does not point to Shieldify yet.

Step 5

Lock down your server

Shieldify can only protect traffic that goes through it. If attackers know your server's own address they can send requests to it directly and skip every check. Close that path:

  • Allow only Shieldify on ports 80 and 443 in your server firewall or your hosting provider's network firewall. Shieldify connects to your server from one address, 63.189.207.48. It is not the address your domain points to: visitors reach Shieldify on the addresses above, Shieldify reaches your server from this one. Changes to it are announced here in advance.
  • Exempt it from automatic blocking too, not only in the firewall: fail2ban (ignoreip), CSF (csf.allow/csf.ignore), your hosting provider's DDoS protection or security panel. Attackers know this address and may send traffic that pretends to come from it so that your server blocks Shieldify; an exempted address cannot be blocked that way.
  • Move to a new IP address if your old one was public for a long time. Old DNS records and history sites keep it findable.
  • Check other records such as mail, ftp or dev that point to the same server and reveal its address.
Step 6

Restore real visitor IP addresses

Behind Shieldify, your server sees requests coming from Shieldify. The visitor's own address and how they connected are forwarded in headers, so your logs, analytics and application can keep using them:

HeaderContains
X-Real-IPThe visitor's IP address.
True-Client-IPThe visitor's IP address.
X-Forwarded-ForThe visitor's IP address, and only that. Whatever the visitor's client sent in this header is dropped, so it cannot be faked.
X-Forwarded-Protohttps or http: how the visitor connected to Shieldify.
X-Forwarded-HostThe hostname the visitor asked for.

Tell your web server to trust these headers only from the address Shieldify connects from, 63.189.207.48. For nginx:

# http {} or server {} block
set_real_ip_from  63.189.207.48;
real_ip_header    X-Real-IP;

For Apache with mod_remoteip:

RemoteIPHeader         X-Real-IP
RemoteIPTrustedProxy   63.189.207.48

Applications with their own trusted-proxy setting (Laravel, Symfony, WordPress plugins, hosting panels) need the same address. Otherwise they see every visitor as Shieldify.

Never trust these headers from every address. Anyone could then send a fake visitor IP straight to your server.

Step 7

Let APIs, webhooks and monitors through

During an attack, new visitors are asked for a browser check or a CAPTCHA. Machine clients such as payment providers, webhooks, mobile apps and uptime monitors cannot complete one. Set them up under Custom rules before you need them:

  • App and webhook paths: a Skip browser checks rule on paths such as /api/* or /payment/callback. These paths never get a browser check or CAPTCHA, while rate limits, bans and your other rules still protect them. The App and webhook paths template adds one; change its paths to yours.
  • Fixed addresses: an Allow rule on Client IP for the published addresses of payment providers, monitors, office VPNs or internal tools (an address range works too). You can also trust an address straight from a request under Traffic; it is added to the Trusted addresses rule.

An allow rule that matches only the client IP or the path is trusted: its traffic skips the DDoS checks, and the firewall still inspects it. An allow rule on anything else, such as a header or the user agent, applies only after the DDoS checks, because anyone can copy those. Keep rules narrow: trust the callback, not the whole website.

Step 8

Set up alerts

Under Notifications, choose where each website's alerts go: email, a Discord channel through a webhook (send a test message from the same page), or both. Each message can be switched on or off:

MessageWhen
Attack wave started and endedAn attack on the website begins and ends, with its duration, peak and the requests stopped.
Automatic mode on and offShieldify switches mitigation on, and off again when traffic is back to normal.
Refused requestsAt most once a day: your website refused most of the form or API requests sent to it, usually forged or automated ones.
Website not respondingShieldify cannot reach your server, and when it answers again. Email only.
Large downloadsAt most once a day: many visitors downloaded large files from your website at the same time, and those downloads were slowed (see Large files and downloads). Email only.
Weekly security reportEvery Monday: last week's requests, blocked traffic, attacks and what Breakwave stopped.
The panel

Seeing what happens

PageWhat it shows
DashboardRequests passed and stopped over time, the latest security events and attacks.
AnalyticsThe requests that reached your website: visitors, pages, countries, browsers, crawlers, referrers, status codes and how much came from the cache.
TrafficEvery request of the last 24 hours with the decision Shieldify made. Search by IP, path, method or status.
Security eventsRequests the firewall stopped, with the rule. Paste a block reference to find the request it names. Fix a false positive from here (see Firewall rules).
Attack wavesEach attack: its size minute by minute, where it came from, the browsers it claimed and what stopped it.

Block references. When Shieldify's firewall, one of your custom rules, rate limits or the Block AI crawlers setting blocks a request, or your server doesn't answer, the page your visitor sees shows a reference such as LYNX-4821-0934-7710. Paste it into the search on Security events to see what happened and which rule it was, with a link to change that rule. Apps that show no page get the same reference in the Shieldify-Ref response header.

Protect

DDoS and automatic mode

The defaults suit most websites. Change them under DDoS and automatic mode:

SettingWhat it does
Automatic learningLearns the website's normal traffic and switches mitigation on by itself when an attack starts. On by default.
SensitivityHow readily automatic mitigation switches on. Normal suits most websites; Low suits websites with large legitimate peaks; High reacts sooner.
Mitigation thresholdWith automatic learning off: the requests per second that switch mitigation on.
Mitigation durationHow long mitigation stays on once it has switched on.
Permanent mitigationKeeps mitigation on until you switch it off, for a known attack campaign.
Per-client rate limitThe most requests per second one address may send before it is slowed down.
Verification during attacksWhat new visitors get while mitigation is on. Automatic: a short browser check, and a CAPTCHA when the attack gets heavy. CAPTCHA: every new visitor solves one.
Strict modeBots posing as ordinary browsers solve a CAPTCHA. Automatic switches it on when needed, Always on keeps it on, Off never asks.
CAPTCHA for automated browsersBrowsers that say they are automated (headless browsers, WebDriver) solve a CAPTCHA before they open pages or send forms.
Stop repeatedly refused requestsWhen your website keeps refusing a client's form or API requests, Shieldify stops that client's requests to that address for a while.
Shared defenseClients recently stopped on another website protected by Shieldify solve a CAPTCHA before they open pages or send forms on yours.
Protect

Firewall rules

The web application firewall blocks exploits such as SQL injection, cross-site scripting and file inclusion with the OWASP Core Rule Set. Under Firewall rules:

  • Protection profile: Low is the recommended default, with the fewest false positives. Medium and High detect more; test your forms and APIs after switching.
  • Applications: turn on the software your website runs (WordPress, XenForo, phpBB, Drupal, Nextcloud, phpMyAdmin, cPanel, DokuWiki). Each one skips only the checks its own admin and editor requests are known to trip, on its own paths.
  • Large request bodies: bodies larger than the firewall inspects are refused (413) by default. Allow them without inspection only if your website needs them.
  • Categories and rules: switch off a single noisy rule or, rarely, a whole category.

A legitimate request blocked? Find it under Security events and choose Skip on this path: the rule keeps protecting the rest of the website. Disabling a rule turns it off everywhere on the website.

Protect

Custom rules

Block, check, allow or redirect requests by path, query string or parameter, method, user agent, header, cookie, host, referer, content type, body size, client IP, country, network (ASN), verified search engine, or whether the website is under attack. A rule has up to five conditions, all or any of which must match. Rules run in order and the first match decides. Each shows its matches in the last 24 hours, and a rule can end by itself after a time you choose.

ActionWhat happens
BlockThe request is refused (403).
ChallengeThe browser check; verified visitors continue.
CAPTCHAThe visitor solves a CAPTCHA once, even after the browser check.
AllowThe request goes through; the rules below and the rate limits are skipped. See trusted allow rules.
Skip firewallThe firewall does not inspect the request. Visitor checks still apply.
Skip browser checksNo browser check or CAPTCHA, for app and webhook paths. Rate limits, bans and the other rules still apply.
RedirectThe visitor is sent to another address. Choose whether to add the path: always this address, the whole path (a website that moved to a new domain), or the rest of the path after where the rule's path starts (a section that moved).
Log onlyOnly counts matches, to try a rule before it acts.

Templates add common rules in one click: WordPress hardening, sensitive files (.env, .git, backups), vulnerability scanners, fake search engines, selected countries only, cloud and hosting networks, app and webhook paths, requests without a user agent, and AI crawlers. Nothing changes until you apply.

Countries and networks: IP Geolocation by DB-IP.

Protect

Rate limits

Limit how often one visitor may call a path, such as a login form or a search page, on top of the website-wide limit. Each limit has a path (/login, or /api/* for everything below it), a number of requests in a time window, optionally the methods to count (for example only POST), and what happens above it: the browser check, a CAPTCHA, or 429 until the window ends.

Add sign-in protection adds limits for sign-in, sign-up and password reset paths in one click; change the paths to your website's before applying. Allowed addresses, verified search engines and requests an allow rule matches are not limited.

Protect

Breakwave, the front line

Breakwave stops attack traffic at the network edge, before it costs anything further up. Under Breakwave you see what it stopped for your website and where attacks came from.

  • Your blocks, instantly: block rules on addresses, countries and networks run on the front line and turn those clients away at once. Rules that look at pages, headers or other request details run in the standard protection.
  • Attack tools and connection floods: known attack tools and clients opening connections faster than any browser are stopped there by themselves.
  • Private mode: only the addresses you list can reach the website; everyone else, search engines included, is turned away. For staging websites and launches that are not public yet. Your Shieldify panel is not affected.
Protect

Zero Trust for admin areas

Under Zero Trust, lock paths only your team should open, such as /wp-admin/* or /admin. List the email addresses that may open each one. A visitor enters their email, Shieldify sends a one-time code only to listed addresses, and with it they stay signed in for the time you choose. Everyone else never reaches your server. Use /path for one page and /path/* for everything under it. To close a whole website, use Breakwave's private mode.

Configure

Caching

Shieldify keeps copies of your files and pages and serves them without asking your server. Without a rule, only static files are cached. Under Caching:

  • Cache rules: cache pages too, or never cache some, by path (/blog/*, *.html). The first rule that matches a path decides how long it is kept.
  • Development mode: skips the cache for three hours, so your changes show at once.
  • Purge: remove the cached copies of some URLs or of everything, so the next visitors get fresh ones.
Configure

Large files and downloads

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. You can be told when it happens: Large downloads under alerts.

  • Hosting large files such as software, packages or videos: serve them from a download server or mirror. Add a Redirect rule for their path, for example starts with /downloads/, and choose Add the rest of the path.
  • Package repositories: package managers cannot pass a browser check. Add a Skip browser checks rule for the repository's path; rate limits, bans and the firewall still apply. Keep the index files on your website and redirect the package files to a mirror: package managers follow redirects and check every file against its hash.

Caching saves your server's work, not network transfer: a large file served from the cache is still a large download.

Configure

Origin

Under Origin, change where Shieldify forwards accepted traffic: the protocol, host and port of your server, and whether www is served by the same website. Use the protocol your server expects: if it moves visitors to HTTPS, set https and port 443 here, or visitors loop between redirects. For an HTTPS origin with a valid public certificate, switch on Verify the origin's certificate; a self-signed or expired certificate then fails with 502. Certificate name sets the hostname sent to your server and checked against its certificate.

WebSockets and server-sent events pass through. If your server answers too slowly or not at all, visitors see a page that retries by itself, and you get the Website not responding alert.

Account

Billing

One subscription covers every website on your account. The base price includes your first domain with up to ten subdomains and one million requests a month; each further domain and each further million requests add to it (see pricing). Only requests that reached your websites are counted. Requests during an attack are never counted, visitors' included.

  • Billing shows the requests counted so far, those left out during attacks, and where the period is heading at the current rate.
  • Monthly limit: set the most you want to pay in a month. At the limit the bill stops growing for the rest of the period and your websites stay protected. We email you at 50%, 80% and 100%.
  • Payment: manage cards and invoices in Stripe. Without payment, protection of your websites pauses; their settings are kept.
Account

Account security

Under your profile, add a passkey (Face ID, Touch ID, Windows Hello or a security key) or an authenticator app for two-step sign-in, and change your password. Your Shieldify account controls who reaches your website: protect it like your hosting account.

Troubleshooting

Common problems

SymptomFix
Panel says the domain does not point to Shieldify yetCheck the record type and target, remove other A and AAAA records, wait for the old TTL to pass, and make sure Cloudflare's proxy is off for that record.
Certificate is not issuedThe domain does not reach Shieldify yet. Fix the record; Shieldify retries by itself.
Webhooks, an app or an API get a browser check or 403 during an attackAdd a Skip browser checks rule on their paths, or an Allow rule on their fixed addresses, under Custom rules.
A form or page is blocked by the firewallFind the request in Security events and choose Skip on this path.
Your logs show only Shieldify's addressConfigure real visitor IPs as in step 6.
Redirect loop ("too many redirects")Shieldify and your server must use the same protocol. If your server moves visitors to HTTPS (an SSL setting in your hosting panel, .htaccess or your application), set the origin under Origin to https and port 443. If your server serves only HTTP on port 80, switch its own HTTPS redirect off and use Force HTTPS under SSL and TLS instead.
Visitors see a page that keeps retrying, or 502Shieldify cannot reach your server: check that your firewall allows 63.189.207.48, that the origin and port under Origin are right, and that your certificate is valid if Verify the origin's certificate is on.
A visitor sent you a reference (LYNX-…)Paste it into the search on Security events: it shows the request and the rule that stopped it, or why your server did not answer.
The website is pausedThe subscription needs a payment. Update the payment method under Billing; protection resumes with your settings.

Still stuck? Open a ticket under Support in the panel, or write to contact@shieldify.ee with your domain and what you see. A person will answer.

Ready WhenYou Are.

Start the 7-day trial and follow this guide to protect your first website.