The Managed Firewall is a key component of our security measures for managed servers and web hosting packages. It is generally managed by our Managed Server Support team.
⚠️ Certain firewall configurations can ONLY be modified on managed servers, not on web hosting packages.
| Description | Web hosting | Managed Server | How to request changes |
|---|---|---|---|
| Modify ports below 1024 | ✖ | ✔ | Authorized support request via konsoleH |
| Modify ports 1024 and above (excluding standard ports) | ✔ | ✔ | konsoleH administration interface |
| Incoming rules (allowing or blocking) can only be configured globally, i.e. for the entire server. | ✖ | ✔ | Authorized support request via konsoleH |
| Outgoing rules (allowing or blocking) can also be configured for individual users. | ✔ | ✔ | konsoleH administration interface |
| Special case for CDNs: Access to websites hosted on the server can be restricted to the CDN's public IP ranges (e.g. Cloudflare, Sucuri, Bunny CDN). In this case, ports 80 and 443 are restricted to these IP ranges, and traffic on these ports is explicitly allowed. | ✖ | ✔ | Authorized support request via konsoleH |
- For security reasons, ports 1024 and above are blocked by default on our web hosting packages and managed servers. You can manage them yourself in konsoleH by selecting the hosting name and navigating to "Services; Open Ports". You can open specific non-standard ports for your hosting there.
Allow- and Blocklist for IP addresses
- Allowlist
- We can configure exceptions for IP addresses in the firewall for specific services or security mechanisms.
- Blocklist
- IP addresses on this list are blocked from accessing certain services on the server.
Temporary blockages
In addition, IP addresses are temporarily blocked by our firewall if, for example:
- they attempt to access suspicious or nonexistent files,
- they make repeated access attempts within a short period of time,
- they repeatedly enter incorrect login credentials (username and password).
It is possible that even seemingly legitimate requests may be blocked. This can happen, for example, if you repeatedly attempt to log in with incorrect credentials — perhaps because you made a typo or forgot your password. Such a security mechanism can also be triggered by incorrectly configured email clients, security scans you perform yourself, or automated access attempts, even though no malicious intent was involved.
If you suspect that your IP address has been blocked in error, please send us an authorized support request from konsoleH. Include your public IP address and, if possible, the error message displayed and the approximate time of the incident. We will then check whether your IP address has been blocked by our firewall. If necessary, we can manually unblock it and add your IP address to a whitelist, depending on the product you are using.
Common Services/Ports
| Port | Service | Application |
|---|---|---|
| 21 | FTPS | File Upload via the FTP Protocol |
| 22 | SFTP | Secure file transfer via SSH |
| 25 | SMTP | Email-Dispatch via SMTP |
| 80 | HTTP | Web Server (Apache / Nginx) |
| 110 | POP3 | Receiving Emails via POP3 |
| 143 | IMAP | Receiving Emails via IMAP |
| 222 | SSH | SSH Remote Shell Access |
| 443 | HTTPS | Web Server (Apache/nginx) via HTTP + SSL/TLS |
| 465 | SMTPS | SMTP + SSL/TLS |
| 587 | SMTPS | SMTP + STARTTLS |
| 993 | IMAPS | Receiving Emails via IMAP + SSL/TLS |
| 995 | POP3S | Receiving Emails via POP3 + SSL/TLS |
| 3306 | MySQL/MariaDB | MariaDB Databases |
| 4190 | Managed Sieve | Email Sieve rules management |
| 5432 | PostgreSQL | PostgreSQL Databases |
A managed server offers you many possibilities: You can host websites and databases on it, as well as send and receive emails. Many customers use their server for several of these tasks at the same time.
If, on the other hand, you use your managed server exclusively for a specific purpose and have outsourced other services (e.g., email), we can close any unnecessary services or the ports required for them upon request. This reduces your server’s attack surface and enhances security.
Possible use cases include, for example:
- Database server: You host only databases on the server. No websites are hosted on it, and the server is not used for sending or receiving email.
- Mail server: You use the server exclusively for sending and receiving emails. No websites or databases are hosted on the server.
- Web server: You host only your websites on the server.
If you use your server exclusively as a web server, the ports for sending and receiving email can be closed. As a result, sending (ports: 465, 587) or receiving (ports: 110, 143, 993, 995) email via your managed server is no longer possible, and the corresponding services are no longer available as potential attack vectors.