ATTACKS COME.
YOUR SITE STAYS UP.
From network floods to HTTP floods, from bad bots to web attacks: everything is stopped before it reaches your server. Your code stays the same and your real IP stays hidden.
Attacks come from everywhere. None reach your server.
The red arcs are attack traffic: they hit the shield in front of your server and break apart. The green ones are your real visitors: they pass straight through.
Four layers, one shield.
Each layer stops what the one before it let through. All in one system, on one dashboard.
- L3Network floods, amplification
- L4SYN and UDP floods
- L5TLS handshake floods
- L7HTTP floods, bots, web attacks
Every second, on your dashboard.
Live traffic, blocked requests, countries and automatic defense, all on your own dashboard in real time.
Not built on someone else's service. Every line is ours.
Every part, from DNS to the shield inside the operating system kernel, is our own software. The numbers:
From L3 to L7, protection at every layer.
Whatever layer an attack comes from, it is stopped before it reaches your server. All in one system, on one dashboard.
Network layer
- ICMP and spoofed-source floods
- Amplification (DNS, NTP, memcached…)
- Fragmented and malformed packets
Transport layer
- SYN, ACK and RST floods
- UDP floods
- Connection exhaustion attacks
Session and TLS
- TLS handshake floods
- Session exhaustion
- Clients impersonating browsers
Application layer
- HTTP GET/POST floods
- Botnets and brute-force logins
- SQL injection, XSS, file disclosure
The difference shows when the attack comes.
Same attack, two different nights.
An unprotected site
With Kernelns
Every request passes through seven layers.
Clean traffic reaches your site; attack traffic is filtered out layer by layer. Hover over a layer.
Network shield. Invalid packets and connection floods are dropped in the operating system kernel, before a connection is ever made.
Solutions that stop attacks before they find you.
From network filtering to the web application firewall, from protected DNS to emergency response: everything that keeps your site up, in one place.
Stops floods in the kernel
When an attack is detected, the defense sets itself up, applies only to the attack's signature and lifts itself once the attack is over.
Exploit attempts stay at the door
OWASP CRS 4 stops SQL injection, XSS, file disclosure and command execution attempts. A rule that raises false alarms can be switched off for your site alone.
Our own nameservers
Your DNS records live with us; proxied records pass through the protection and your real IP stays hidden. Existing records are scanned and imported, and SSL is issued automatically.
Under attack? Right away.
You talk to a person, not a ticket system. We put your site under protection the same day and do the setup together with you.
The story of every request, on your dashboard.
What came in, where it came from, why it was stopped. Writing a rule or switching on attack mode takes seconds.
| Time | IP | Country | Path | Result | Reason |
|---|---|---|---|---|---|
| 21:40:12 | 88.241.18.7 | TR | GET /product/482-leather-bag | passed | — |
| 21:40:13 | 185.220.101.4 | NL | GET /?id=1' OR '1'='1 | blocked | WAF · SQL injection |
| 21:40:15 | 45.95.147.12 | RU | POST /wp-login.php | blocked | rate limit · 1 h ban |
| 21:40:19 | 66.249.66.1 | US | GET /category/women | passed | Googlebot · verified |
| 21:41:02 | 103.152.x.x ×18,400 | — | GET / (flood) | challenge | automatic defense |
| 21:41:07 | 194.26.29.40 | CN | GET /../../etc/passwd | blocked | WAF · file disclosure |
| 21:41:09 | 78.180.42.15 | TR | GET /cart | passed | passed the challenge in 2 s |
Actions taken
# put a new site under protection curl -X POST https://…/api/v1/zones \ -H "Authorization: Bearer knt_…" \ -d '{"name":"example.com","defaults":true}' # switch on attack mode curl -X PATCH https://…/api/v1/zones/12 \ -d '{"settings":{"under_attack":true}}' # block an IP curl -X POST https://…/api/v1/iprules \ -d '{"zone_id":12,"kind":"ip","value":"198.51.100.23","action":"block"}'
A person does the setup, together with you.
Your site doesn't move and your code doesn't change. It is usually done within a few hours.
Let's talk
Tell us about your site and the problem you're facing. No technical preparation needed.
We do the setup
We add your domain, scan your existing DNS records and tune the protection to your site.
Protection starts
You change two nameserver addresses. Traffic flows through us, SSL is issued automatically and your dashboard goes live.
Under attack right now?
Don't wait. Let's protect your site today; we'll import your records and do the setup together with you.
Frequently asked questions
Will my site go down during an attack?
Preventing that is the whole point. Attack traffic is stopped before it reaches your server; during a very heavy attack, visitors keep getting in after a browser check that takes a few seconds.
Will it affect my Google rankings?
No. Real search engine bots are verified and let in without hitting any rule. Only fake bots pretending to be Google are stopped.
Does it work with WordPress, cPanel, hosted e-commerce…?
Yes. Kernelns doesn't care what your site is built with; it meets the web traffic in front of it. Shared hosting, a VPS or your own server: it makes no difference.
Will it slow my site down?
In normal times visitors never see a challenge. Static files can be served from cache and pages are compressed, so your server is relieved of unnecessary load too.
I have more than one site.
You manage them all from one dashboard, with separate rules and settings for each. You can also add many sites at once through the API.
How much does it cost?
It depends on the number of sites and your traffic. Tell us about your site and what you need using the contact below, and we will send you a custom price.