How your protection with HackShield works

HackShield protects your appearance with four complementary building blocks. In the following tabs we present the core functionalities.


IP testing

With HackShield, you stay in control. IP addresses of attackers can be blocked automatically. Access from countries or the TOR network can also be temporarily restricted. The duration of the blocking can be determined individually. In addition, you can maintain and manage your own blacklist or whitelist. Optionally, a cloud protection detects attacks in our network and protects all participants preventively.


Pare-feu d'application Web (IDS/IPS)

The Intrusion Detection System (IDS) also detects attacks and logs them. An automatic subdivision into different degrees of severity takes place. Depending on the severity of the attack, you can be informed about it and immediately defend yourself automatically and actively against it with our Intrusion Prevention System (IPS).


brute force defense

HackShield recognizes unauthorized login attempts into the backend of your shop or content management system based on various parameters. If a user name does not exist during a login attempt or if, for example, login attempts to a user from different IP addresses take place in a certain time window, the determined IPs can be temporarily and automatically blocked.



The importance of regular updates should be known to every website operator today. It is not without reason that the legislator has reacted here and created regulations. The update check checks once a day whether a new version of your software is available. As soon as this is the case, HackShield will inform you about this update.

Whether 1 or 100 manages appearances: With HackShield you'll never miss an important update again!


file integrity check

The entry gates for a hacker are manifold. A hacked FTP account, an unresolved vulnerability in the server software, a forgotten software from the developer or a plugin with a previously unknown vulnerability: If a hacker attack is successful, certain files in the Webroot and in the core of your system are usually modified.

We check daily for changes and report these as soon as they become known.


Suspicious files

There are files that just shouldn't be there. These include database dumps, files that can be used to access databases, backups of personal data, or files that have been dropped by hackers.

We check the Webroot daily for such files and inform you when something appears that doesn't belong there.



Checking HTTP Status Codes

A simplified HTTP status code indicates what happens when a visitor visits your website via a browser. Normally we expect a status code of 200, which indicates that the visitor's request was successful. I.e. the visitor wants to call your start page and the server on which your appearance is hosted returns this start page.

HackShield monitors the accessibility of your home page and up to 100 subpages and informs you if an unwanted status code is delivered.


Contrôle de l'indexation rampante

From a search engine optimization (SEO) point of view, all essential pages of your website should be accessible to search engines. From the point of view of data protection and warning protection, special pages (e.g. imprint, general terms and conditions) should better not appear in the results of search engines. The robots.txt, the Robots meta tags and the X-Robots tag HTTP header take over this control.

HackShield monitors the settings for the home page of your website and up to 100 other URLs in your environment.


Measure server response time

The response time of your server has an immediate influence on the loading speed of your web pages. The loading speed in turn is an important ranking criterion for Google (SEO). Due to Mobile First indexing from July 2019, loading time will also become increasingly important.

HackShield monitors the loading time of your homepage and 100 other URLs and informs you if the loading time is too long. There is virtually continuous control of your hosting environment.


Check SSL Certificate

Every internet presence should have an SSL certificate, so that your website is not only accessible via http, but also via https. If you operate a shop, offer a login, a registration or a contact form, an SSL certificate is also legally binding. However, certificates expire regularly and must be renewed. It can also happen that your website can also be accessed without SSL despite the certificate. Your certificate may have been incorrectly merged, or the certification authority may no longer be trusted.

No matter what happens, HackShield checks your certificate daily and notifies you of any discrepancies.


Naviguer en toute sécurité

Google Safe Browsing protects over 4 billion devices every day by alerting users to obviously hacked websites and warning them of dangerous files (such as malicious code).

HackShield continuously checks the status of your Google Safe Browsing presence and notifies you when Google issues warnings about your site. This way you also protect your already worked out positions with regard to the ranking in the search engines. If Google is already warning you of your presence in whole or in part, it's high time to identify and fix the cause(s).


Vérification de la liste noire IP

If it is possible to send e-mails directly from your server or from your web space, the IP address of your hosting environment may end up on a blacklist.

The causes can be that you or another company hosting on the same server, for example, have sent many e-mails to many invalid recipients, for example in the form of a newsletter. Or your webspace or that of another customer on the server was hacked and a spammer now sends masses of e-mails. In any case, it is important that such an incident is quickly identified and the cause rectified.


HTTPS as default setting

HTTPS encrypts almost all information exchanged between client and web service. Properly configured, it guarantees three things: confidentiality, authenticity, integrity

DSGVO: Recital 83, Art. 5.1.f, Art. 25, Art. 32.1 According to DSGVO Art. 25, a controller is responsible for the enforcement of data protection already in the development phase and in standard settings at the current state of the art. Encrypted connections are an established technology to protect the privacy of website visitors from eavesdropping attacks.


HTTP Sûreté de transport stricte

HTTP Strict Transport Security (HSTS) is a widely supported standard for protecting a visitor by ensuring that the web browser can only open a page via HTTPS at all times. HSTS eliminates the uncertain need to redirect a visitor from http:// to URLs.

If the browser is told that a domain is using HSTS, it does two things: It always uses a https:// connection, even if a http:// link was clicked or if a domain was entered in the address bar without a protocol. It removes the ability for users to ignore warnings about invalid certificates.


Politique de sécurité du contenu

A Content Security Policy (CSP) provides an additional layer of security that helps detect and mitigate attacks, including cross-site scripting (XSS) and data injection attacks. Such types of attacks are likely to deface a Web site and allow data theft and the spread of malware.

DSGVO: Recital 83, Art. 5.1.f, Art. 25, Art. 32.2 - DSGVO Art. 32.2 clarifies that measures must be taken against unauthorised disclosure or access to the personal data transmitted, stored or otherwise processed.


Referrer Policy Check

Referrer headers are a privacy nightmare because they allow Web sites and services to track visitors across the Web and reveal browsing habits (and thus possibly private, sensitive information), especially when combined with cookies.

DSGVO: Recital 83, Art. 5.1.c, Art. 25, Art. 32.2 Setting up a Referer Directive is a quick and easy way to minimise data (Art. 5.1.f) and ensures that data is not transmitted unnecessarily or inadmissibly (Art. 32.2).



HTTP Header Checking

The header test is based on the Mozilla HTTP Observatory Scanner (Mozilla Public License 2.0) by April King, implemented by us for HackShield by Webbkoll. This is about checking the delivered data. For example, it is about telling a browser whether a page can be displayed in a frame, iframe or object. These headers help to minimize the risk of data misuse.

DSGVO: Art. 5.1.c, Art. 5.1.f, Art. 25, Art. 32.1-2.




cookie checking

The storage of information or access to information stored on visitors' devices, e.g. in the form of cookies, is subject to sui generis legislation in the European Union (ePD, Art. 5.3). These sui generis laws distinguish between information that has technical features stored and information that is stored in support of commercial features.

DSGVO: Recital 60, Recital 61, Recital 69, Recital 70, Recital 75, Recital 78, Article 5.1.a, Article 5.1.c, Article 5.1.e, Article 21, Article 22, Article 32.