Policies

2024 20 Feb

Tor exit-node policy

If you are using our services to provide an Tor exit node please be advised that only the following exit policies are permitted to use on our premises. Any exits using other policies will be suspended as Terms of Service violators. Reduced Exit policy ExitPolicy accept *:20-21 # FTP - File Transfer Protocol (data / control) ExitPolicy accept *:43 # WHOIS - who is query and response protocol ExitPolicy accept *:53 # DNS - Domain Name System ExitPolicy accept *:79 # finger - Name/Fin[...]

0.81 Read more...
2023 15 Sep

Vulnerability Reporting

1. Introduction: This policy outlines the process for third-party hackers, security researchers, and the general public to responsibly disclose vulnerabilities they discover in our systems, software, or services. We value the contributions of the security community and recognize the importance of their role in maintaining the highest security standards. 2. Scope: This policy applies to any digital assets owned, operated, or maintained by ServerAstra. This includes websites, applications, servers, and other [...]

0.47 Read more...
2023 19 Mar

Network Security policy

At ServerAstra, we take the security of our customers' data and network very seriously. To ensure the highest level of protection, we employ several measures, including blocking outgoing Simple Mail Transfer Protocol (SMTP) port 25 and automated abuse monitoring. This page provides detailed information on our policies and the reasons behind them. Table of Contents SMTP Port 25 Blocking Policy Firewall Protection Automated Abuse monitoring Benefits of Our Network Security Measures FAQs SMTP Port 25 Block[...]

0.97 Read more...
2022 17 Feb

ServerAstra Peering policy

ServerAstra AS56322 has an open peering policy and will peer with networks at mutual exchange points in accordance with the policies described below Please read these policy carefully and thoroughly. Requirements ServerAstra uses PeeringDB as a single authoritative source of truth. This means peering partners must have an up-to-date PeeringDB entry before a bilateral peering session can be established. ServerAstra will use industry standards to secure the peering sessions. This includes industry standard pr[...]

0.29 Read more...
2019 14 May

Cloud Resource policy

Stellar and Stellar Pro Cloud Resource policy CPU For Central Processing Unit configuration in our cloud platform we use Dual AMD Epyc 7401 or Single AMD Epyc 7401P for each host node The difference between v(irtual)CPU and d(edicated)CPU is the core usage guarantee. vCPU means maximum 100% of 1x AMD Epyc 7401 Core and minimum 50% expressed by formula: vCPU := 100% >= (1 x hostCPU) >= 50% dCPU means 100% of dedicated 1x AMD Epyc 7401 Core expressed by formula: pCPU := 1 x hostCPU hostCPU is 1 Core of [...]

0.44 Read more...