Terms and Conditions

1. Definitions

For the purposes of this Agreement, the following terms shall have the meanings set forth below:

"Provider" means S.C. DreamServer S.R.L., VAT ID: 29975003, CIF: RO36208038, EUID: ROONRC.J2012003481409, with registered office at Str. Mircea Vulcanescu, Nr. 2, Et. 7, Ap. 25, Sector 1, Bucharest, Romania.

"Client" means any natural person (aged 18 or older) or legal entity that registers an account with, orders, or uses services provided by the Provider.

"Services" means all services offered by the Provider, including but not limited to dedicated servers, virtual servers, domain registration, LIR services, internet exchange services, reseller services, and any related products or features.

"Dedicated Server" means a physical server (Blade, Enterprise, Game, or Micro) provided by the Provider and hosted in the Provider's datacenter.

"Virtual Server" means a virtualized server instance, either container-based (VPS LXC) or fully virtualized (VDS KVM), provisioned on the Provider's infrastructure.

"Domain" means an internet domain name registered through the Provider acting as an accredited RoTLD registrar or through third-party registries.

"IP Resources" means IPv4 addresses, IPv6 prefixes, ASN numbers, and other internet number resources allocated or assigned through the Provider's RIPE NCC Local Internet Registry (LIR).

"DSIX" means the DreamServer Internet Exchange peering platform, operated by the Provider under AS58218.

"RTBH" means Remotely Triggered Black Hole filtering, the Provider's network-layer DDoS mitigation mechanism described in Article 16.

"Datacenter" means the Provider's own datacenter facility located in Bucharest, Romania, where Services are hosted and operated.

"Agreement" means these Terms and Conditions together with the applicable Service Level Agreement (SLA), Privacy Policy, and any service-specific addenda or order forms.

2. Scope of Services

The Provider offers the following categories of services, all hosted and operated from its own Datacenter in Bucharest, Romania:

Dedicated Servers: Blade Servers, Enterprise Servers, Game Servers, and Micro Servers, each with specifications as described on the Provider's website.
Virtual Servers: VPS (LXC container-based virtualization on Proxmox) and VDS (KVM full virtualization), available in various configurations.
Domain Registration: Registration, renewal, and management of .ro domain names through the Provider's accreditation with RoTLD, as well as other TLDs through partner registries.
LIR Services: Allocation and assignment of IPv4/IPv6 prefixes, ASN numbers, and other IP resources through the Provider's RIPE NCC membership.
DSIX Internet Exchange: Free peering access to the DreamServer Internet Exchange operating under AS58218.
Reseller Services: White-label and reseller access to the Provider's infrastructure under dedicated reseller agreements.

Technical specifications of each service are detailed on the corresponding product page at dreamserver.ro and in the applicable order confirmation or contract.

3. Account Registration & Client Obligations

Acceptance of Terms. Your mere presence on dreamserver.ro, the act of creating an account, ordering any Service, or otherwise using the Site or Services constitutes your explicit acknowledgement that you have read, understood, and agreed to these Terms and Conditions, the applicable SLA, and the Privacy Policy in their entirety. If you do not agree with any part of this Agreement, you must not access the Site, order Services, or create an account.

To use the Services, the Client must create an account through the Provider's client area at dreamserver.ro/client/. Upon registration, the Client agrees to the following obligations:

Provide accurate, complete, and current personal or corporate information, including legal name, address, email, telephone number, and (where applicable) VAT identification number.
Update account information promptly whenever changes occur.
Be at least 18 years of age or possess legal capacity to enter into binding agreements.
Maintain the confidentiality and security of account credentials. The Client is solely responsible for all activities conducted under their account.
Comply with all applicable laws of Romania, the European Union, and the jurisdiction in which the Client is located.
Promptly notify the Provider of any unauthorized access to or use of the Client's account.
Maintain a valid abuse contact (email and, for BGP customers, abuse-c in RIPE) reachable 24/7.

The Provider reserves the right to verify the identity of any Client (KYC) and to refuse or terminate accounts that contain false or misleading information.

4. Orders, Activation & Service Delivery

Services are ordered through the Provider's website or client area. Each order constitutes an offer to purchase, which becomes binding upon confirmation by the Provider and receipt of payment.

Standard activation timelines

VPS (LXC) and VDS (KVM): automated provisioning, typically within minutes of payment confirmation.
Dedicated Servers (in stock): provisioned within 24 hours of payment confirmation for standard configurations.
Custom or out-of-stock configurations: may require 2–5 business days; the Provider will communicate the estimated delivery time.
Domain registration: processed within 24 hours, subject to registry availability and validation requirements.
LIR Services (new prefix/ASN requests): subject to RIPE NCC processing times, typically within 5 business days.
DSIX port provisioning: within 24 hours of approval for eligible ASNs.

Setup fees may apply to certain services and will be clearly indicated at the time of order. Setup fees are non-refundable once the service has been provisioned.

5. Pricing, Payment & Billing

All prices are denominated in EUR (Euro) unless otherwise specified on the order form. Prices listed on the Provider's website are exclusive of VAT unless stated otherwise. VAT is applied at the prevailing Romanian rate for clients without a valid intra-community VAT number. Clients with a valid EU VAT number in a member state other than Romania are subject to the reverse charge mechanism.

Services are billed in advance on the selected billing cycle (monthly, quarterly, semi-annually, or yearly depending on the plan). Invoices are issued electronically and delivered by email at least 7 days before the due date. Payment may be made by bank transfer (EUR or RON), credit/debit card, PayPal, or other methods available in the client area.

Non-payment escalation

7 days overdue: the Provider sends a payment reminder.
14 days overdue: the Provider may suspend the affected Services. Data is preserved during the suspension period.
30 days overdue: the Provider may terminate Services and permanently delete all data associated with the Client's account. The Provider bears no liability for data loss resulting from termination due to non-payment.

6. Acceptable Use Policy

The Client agrees to use all Services in full compliance with applicable Romanian and European Union legislation. The following activities are strictly prohibited:

Sending unsolicited bulk email (spam) or operating open mail relays.
Distribution, hosting, or transmission of malware, viruses, trojans, ransomware, or any other malicious software.
Initiating, facilitating, or participating in Distributed Denial of Service (DDoS) attacks or any form of network attack.
Hosting, storing, or distributing illegal content under Romanian or EU law, including but not limited to child sexual abuse material, content inciting terrorism, or content promoting hatred or violence.
Hosting content that infringes on copyright, trademarks, or other intellectual property rights of third parties.
Cryptocurrency mining on shared or virtual server infrastructure (VPS/VDS/Micro) without prior written approval. On dedicated Enterprise/Blade/Game servers mining is permitted subject to power and heat limits.
Port scanning, network probing, or vulnerability scanning of third-party systems without their explicit authorization.
IP address spoofing, BGP hijacking, route leaks, or any form of network identity falsification.
Operating Tor exit nodes without prior written approval from the Provider.
Phishing, social engineering, identity theft, or any form of online fraud.
Hosting of proxy, VPN, or traffic-anonymization services used as a primary vehicle for abuse towards third parties.
Running public-facing DNS open resolvers, NTP amplifiers, memcached servers exposed to the internet, or any other service that can be exploited for reflection/amplification attacks.

Upon detection of any violation, the Provider may immediately suspend the affected Services without prior notice and without refund. The Client will be notified of the violation and, where appropriate, given a reasonable opportunity to remediate. Repeated or severe violations will result in immediate and permanent termination of all Services without refund.

7. Fair Use & Resource Limits

Each Service is subject to the resource limits specified in the applicable plan or configuration, including bandwidth, CPU, RAM, and storage allocations.

VPS (LXC) resources are shared among multiple clients on the same Proxmox host. The Provider does not guarantee exclusive access to physical hardware resources. The allocated vCPU, RAM, and storage represent the Client's guaranteed minimum share, but actual performance may vary depending on overall system load. The Provider may migrate a VPS to a different host at any time for maintenance or load balancing, with minimal or no downtime.

VDS (KVM) allocations (vCPU, RAM, storage) are dedicated to the Client's virtual machine. CPU is still share-oriented, RAM and storage are exclusive. Live migration between hosts may be performed for maintenance with no visible interruption.

Dedicated Servers give the Client exclusive access to all physical hardware resources of the assigned server.

Bandwidth policy

Bandwidth allowances per plan are published on the relevant product page (e.g., 10 TB/month for Micro, 20 TB/month for Enterprise). After exceeding the allowance, the Provider may (a) apply pay-per-GB overage at the published rate, (b) throttle the port to a lower speed, or (c) request an upgrade to a higher tier; the Provider will contact the Client before taking action where practical. Sustained traffic patterns that adversely impact other clients' network performance may be throttled regardless of the per-plan allowance.

9. SLA & Uptime

The Provider commits to 99.9% network and infrastructure uptime for all hosted services, measured on an annual basis. The detailed terms of this commitment, including credit calculations, exclusions, and claim procedures, are set forth in the separate Service Level Agreement.

The Provider reserves the right to perform scheduled maintenance during designated maintenance windows. The Client will be notified at least 48 hours in advance of any planned maintenance that may affect service availability.

The SLA does not apply to interruptions caused by force majeure events (Article 23), Client-initiated actions, Client hardware upgrades, or third-party ISP outages between the Client and the datacenter.

10. Backups & Data Responsibility

The Client bears sole responsibility for maintaining regular backups of all data stored on the Provider's infrastructure. The Provider strongly recommends that the Client implement an independent backup strategy using off-site storage.

The Provider offers optional backup services for some VPS/VDS plans. Where included, the Client may request free periodic backups as described in the applicable service plan. However, the Provider does not guarantee the completeness, integrity, or recoverability of any backup data.

Under no circumstances shall the Provider be held liable for loss of data, regardless of cause, except where such loss is directly attributable to the Provider's gross negligence or willful misconduct.

For Dedicated Servers, the Provider does not perform backups. The Client has full root access and must implement their own backup strategy (rsync to a second server, ZFS snapshots, LVM snapshots, managed backup service, etc.).

11. Dedicated Servers (Blade, Enterprise, Game, Micro)

Dedicated Servers are physical machines owned and operated by the Provider, hosted in the Provider's Datacenter and rented to the Client for the duration of the subscription.

Hardware ownership

All physical hardware remains the exclusive property of the Provider. The Client has no right to physical access, inspect, modify, or retrieve the physical hardware, except where expressly granted under the Loyalty Gift Program (Article 15).

Hardware replacement

In the event of hardware failure, the Provider will replace the defective component (drive, RAM, power supply, NIC, motherboard, etc.) or the entire chassis with an equivalent unit at no cost to the Client. Replacement downtime target is 12–24 hours during business days for critical failures, with priority handling for Enterprise and Blade customers. Data on drives is preserved where technically possible; if the primary drive fails, the Client must restore from their own backups.

Included with every dedicated server

Dedicated public IPv4 and IPv6 allocations as per the plan.
Free DSIX peering port (1 Gbps or 10 Gbps depending on the plan).
Out-of-band remote management (iLO/IPMI/IMM/iRMC) via VPN, see Article 13.
RTBH DDoS mitigation on the uplinks (Article 16).
24/7 NOC access for network and infrastructure incidents.

Line-specific notes

Blade Servers: hosted in HP ProLiant BladeSystem c7000 enclosures with Virtual Connect Flex-10 interconnects and Cisco Nexus vPC. Minimum RAM configuration is 192 GB ECC.
Enterprise Servers: 1U/2U rack servers with Dual-Port Active-Active vPC on Cisco Nexus. Optional Intel X710-DA 10 GbE NIC upgrade.
Game Servers: high-frequency CPU selection (i7-3770, i7-4790, Ryzen 9 3900X, i9-10900K) optimized for single-thread performance. 128-tick CS2 capable.
Micro Servers: low-power bare metal (Intel Celeron N2807 or AMD G-T48E) with 8 GB RAM and 128 GB SSD on a SATA adapter. Annual billing.

12. Virtual Servers (VPS LXC & VDS KVM)

VPS (LXC)

VPS instances are Linux containers provisioned on a shared Proxmox host. The Client receives root access within the container, but the kernel is shared with the host. Certain kernel-level operations (custom kernel modules, raw socket programs requiring elevated privileges, specific nested virtualization) are not possible inside a VPS. For those workloads choose a VDS or Dedicated Server.

VDS (KVM)

VDS instances are full virtual machines on KVM with dedicated vCPU, RAM, and storage. The Client may run any supported guest OS, install custom kernels, and perform raw-socket operations. VDS instances do not support hardware passthrough (GPU, PCIe) except by separate arrangement.

Resource overcommit

The Provider does not overcommit storage or RAM on either VPS or VDS. CPU is committed-at-steady-state but may burst; sustained 100% vCPU use across many neighbours on the same host may cause temporary contention.

IP addresses

Each VPS/VDS ships with one dedicated IPv4 address and one IPv6 /64. Additional IPs are available on request at the published per-IP fee, subject to RIPE policy justification.

Outbound email (SMTP)

Outbound TCP port 25 (SMTP) is blocked by default on all VPS and VDS Services as an anti-spam and IP-reputation measure, consistent with the practice of major cloud providers. Authenticated mail submission on ports 587 and 465 remains available, so legitimate mail can still be sent through an authenticated relay. The block may be lifted only on explicit, justified request and at the Provider's sole discretion, subject to the conditions set out in Section 18 (IP Reputation, Anti-Spam & Blacklists).

13. Remote Management & OS Installation

Out-of-band management (Dedicated Servers)

Each dedicated server ships with access to its out-of-band management controller (iLO on HP, IPMI on Dell, IMM on IBM, iRMC on Fujitsu) reachable only through a dedicated VPN tunnel provisioned by the Provider. The Client is responsible for keeping VPN credentials confidential. Exposing the OOB interface to the public internet is prohibited and the Provider reserves the right to block such traffic.

Custom OS / ISOs

The Provider offers a library of ready-to-install ISOs (Debian, Ubuntu LTS, AlmaLinux, Rocky Linux, Devuan, FreeBSD, OpenBSD, Proxmox VE, Windows Server 2019/2022, VMware ESXi, etc.). The Client may also upload a custom ISO to the client area; the Provider will stage it on the server for installation via the OOB console.

Managed services (optional)

The Provider offers optional managed services (OS installation assistance, hardening, control panel setup, monitoring, patching) under separate hourly or monthly pricing. Unless explicitly contracted, all services are unmanaged: the Client is responsible for OS administration, security patches, application-layer configuration, and data backups.

14. Hardware Upgrades & Modifications

Available upgrades for dedicated servers include additional RAM, additional drives (SATA/SAS/SSD/NVMe), Intel X710-DA 10 GbE NIC (Enterprise and Blade lines), additional IPv4/IPv6 allocations, and upgraded DSIX port speed.

Upgrades are priced per component. IP additions are hot-path with no downtime. Physical upgrades (RAM, drives, NIC) require a scheduled maintenance window typically lasting 15–30 minutes, coordinated in advance with the Client. Micro Servers have a fixed configuration and cannot be upgraded in RAM, CPU, or onboard storage (external USB drives remain the Client's property and are not covered by upgrades).

Any hardware upgrade performed by the Provider remains the property of the Provider and is subject to the same ownership rules as the base server (Article 11). Upgrades added during the rental are not included in the Loyalty Gift (Article 15).

15. Loyalty Gift Program

Servers marked with the Loyalty Gift badge on the product page are eligible for the Loyalty Gift Program. After 12 consecutive months of uninterrupted rental, the Client becomes entitled to receive the physical server as a gift from the Provider, free of charge.

What the gift includes

The physical server chassis and CPU(s) listed on the product page.
A single 128 GB OS SSD (the drive originally shipped with the server; for Micro servers this is the 128 GB SSD on a SATA adapter).
The minimum RAM configuration originally listed on the product page (for Micro servers this is the full 8 GB, since the chassis does not support more).

What the gift does not include

Additional RAM modules added during the rental.
Extra storage drives (HDD, SSD, NVMe, external USB disks) beyond the OS drive.
Network card upgrades added during rental (for Game Servers, the Fujitsu D2735 enterprise NIC is removed before handover; the server ships with the motherboard onboard network port only).
Any other components added during the rental period.

⚠ No warranty after handover. Once the Client picks up the gifted server, the Provider provides no warranty or technical support for the hardware. The server is provided as-is, free of charge, and the Provider bears no liability for any subsequent hardware failure or issues.

"Uninterrupted rental" means no suspension due to non-payment, no service termination initiated by either party, and no material downgrade. A transfer to a different server of the same line resets the 12-month counter. Pickup logistics (courier arrangement, in-person collection at the datacenter, or Provider-arranged shipping at Client's expense) are coordinated individually after the 12-month milestone.

16. RTBH DDoS Mitigation

The Provider operates Remotely Triggered Black Hole (RTBH) filtering on its BGP uplinks, continuously monitored via sFlow telemetry. When traffic to a destination IP spikes above baseline, the sFlow collector detects the anomaly in real time and a blackhole route is triggered over iBGP. The blackhole community is automatically announced to upstream Transit Providers, and the attack traffic is dropped at their network edge before reaching the Provider's network.

Scope & limits

RTBH is effective against volumetric L3/L4 floods (UDP, SYN, amplification, reflection). It is the standard network-operator defense used by every serious ISP and datacenter.
While RTBH is active on a given IP, that IP is unreachable from the internet for the duration of the blackhole. The Client's other IPs and services remain unaffected.
Layer 7 application-layer attacks (HTTP floods, slowloris, application-logic abuse) fall outside the scope of RTBH and require application-level defenses (WAF, rate limiting, caching, CDN) that the Client implements at their own application tier.
RTBH is included at no additional cost on all Services covered by these Terms.

How it is triggered

RTBH is triggered automatically by the sFlow collector when traffic to a destination IP exceeds the configured anomaly threshold. The Client may also request manual triggering by emailing noc@dreamserver.ro or, for BGP customers, by announcing a blackhole community on their iBGP session. The Provider publishes the accepted blackhole communities and the validation policy in the DSIX documentation.

17. IP Resources & LIR Services

IP Resources allocated or assigned through the Provider's RIPE NCC LIR are subject to the following conditions:

All IP addresses, IPv6 prefixes, and ASN numbers remain the property of RIPE NCC and are allocated under the terms of the RIPE NCC Service Agreement and applicable RIPE policies.
The Client must comply with all applicable RIPE NCC policies regarding the use, registration, and documentation of assigned resources, including maintaining accurate abuse-c contact information.
IP Resources are provided for use with the Provider's Services. Upon termination of the underlying service, IP Resources will be revoked and returned to the Provider's pool unless a separate LIR sponsorship agreement is in place (see LIR Services).
Under a sponsorship agreement, the Client may keep their own PI (Provider Independent) resources, ASN, and RIPE membership, with the Provider acting as sponsoring LIR. Sponsorship is invoiced annually and is subject to a separate contract.
The Provider may revoke IP Resources if the Client violates RIPE NCC policies, this Agreement, or applicable law, or if the resources are used in abuse activities documented by a valid complaint.

17.1 IPv6 Specific Obligations

IPv6 sub-allocations carved from the Provider's RIPE NCC allocation (2a10:fa80::/29) are additionally governed by the policies referenced below. By ordering an IPv6 lease the Client and any downstream sub-assignees expressly accept the following:

End User definition. The Client must be a registered legal entity (SRL, SA, PFA, GmbH, Ltd., NGO), public body, or a natural person operating its own network, with a bona-fide technical need for IPv6 address space ("End Site" as defined in RIPE-738, Section 2.9).
Geographic scope. The RIPE NCC service region covers over 75 countries in Europe, the Middle East and parts of Central Asia (official page at ripe.net/about-us/what-we-do/ripe-ncc-service-region/). At least a substantial part of the Client's deployment using the assigned IPv6 prefix shall remain within this service region. Operations entirely outside the RIPE region should obtain address space from the regional registry serving that area (ARIN for North America, APNIC for Asia-Pacific, LACNIC for Latin America and the Caribbean, AFRINIC for Africa). The Provider may decline or terminate a lease where it determines the assignment is used predominantly outside the RIPE service region.
Sub-assignment. Prefixes registered as ALLOCATED-BY-LIR may be sub-assigned by the Client to its own downstream end customers, under conditions equivalent to those imposed by this section. Prefixes registered as ASSIGNED PI shall NOT be sub-assigned to third parties (RIPE-738 Section 2.6 and RIPE-637). Providing individual host addresses on a link operated by the Client is not considered a sub-assignment.
Assignment sizes. The Client shall follow RIPE-738 Section 5.4: never smaller than /64 per subnet, recommended /48 per end-site, /56 per residential customer, /64 per single LAN. Assignments larger than /48 require a separate ASSIGNED object registered by the LIR.
RIPE Database registration. The inet6num, route6, org, mntner and role (abuse-c) objects associated with the assignment shall be kept accurate at all times. The Client shall notify the Provider within 14 days of any change of organisation name, address, technical contact or abuse-c contact (RIPE-738 Section 5.5).
Acceptable Use. The Client shall not use the assigned IPv6 space for spam, phishing, malware distribution, command-and-control, denial-of-service attacks, child sexual abuse material, BGP hijacking, route leaks, or any activity prohibited by EU or Romanian law. RPKI ROA shall match the announcing ASN, no announcement of prefixes outside the assignment is permitted.
Abuse handling. The Client shall reply to abuse reports addressed to its abuse-c within 24 hours. Failure to respond, failure to remediate confirmed abuse, or repeat offences authorise the Provider to apply blackhole filtering on the affected /48, suspension or full revocation of the prefix.
Annual fee & resource return.
1. PA sub-allocations (ALLOCATED-BY-LIR, the standard lease): the Client pays the annual fee to the Provider. Where the fee is unpaid after a 30-day grace period, or the Client cannot be reached, the Provider shall revoke the sub-allocation and return the prefix to its own 2a10:fa80::/29 allocation pool. The Client must renumber out of the affected block before the revocation effective date.
2. PI sponsorships (ASSIGNED PI, separate sponsorship contract): pursuant to RIPE-637, where the Client cannot be contacted or fails to pay the annual fee after the grace period, the resources are returned to the RIPE NCC by default.
End User Assignment Agreement. By accepting these Terms, the Client is bound by the RIPE NCC End User Assignment Agreement (RIPE-548) as incorporated by reference. The full text of applicable RIPE policies is available at ripe.net/publications. RIPE policy documents may be revised through the RIPE Policy Development Process (PDP), the latest applicable version applies.
Termination & portability.
1. PA sub-allocations are not portable to another LIR (they are sub-allocations from the Provider's own RIPE block). Upon voluntary termination, the Client shall renumber its services to another address block within the notice period. The reclaimed prefix returns to the Provider's 2a10:fa80::/29 pool.
2. PI assignments held by the Client under sponsorship may be transferred to another RIPE NCC member LIR within 30 days of termination. Failure to complete the transfer in this window results in the resource being returned to RIPE NCC by default.
3. The IP space itself remains the property of RIPE NCC at all times; the lease grants a right of use, not ownership.

Reference RIPE policy documents

RIPE-738: IPv6 Address Allocation and Assignment Policy
RIPE-637: Contractual Requirements for Provider Independent Resource Holders
RIPE-548: RIPE NCC End User Assignment Agreement
RIPE-826: IPv4 Address Allocation and Assignment Policies (applies to IPv4 portions of the service)
RIPE NCC: End User Requirements (operational summary)
RIPE NCC Standard Service Agreement

18. IP Reputation, Anti-Spam & Blacklists

This Section applies to every Service that includes one or more IP addresses: dedicated servers, virtual servers (VPS LXC and VDS KVM), micro-servers, colocation, IPv6 leases, and any future product where an IPv4 or IPv6 address is delivered by the Provider. The Provider does NOT sell IP reputation, it leases addresses from its own RIPE NCC allocation pool. The Client expressly acknowledges and accepts the clauses below as a condition of receiving any IPv4 or IPv6 address through any Service.

IP addresses are a shared, recyclable resource. IPv4 in particular has been actively reused since the 1980s, IPv6 since the 2000s. Any address the Provider allocates may have been previously held by another organisation whose past activity, legitimate or otherwise, may be recorded in third-party reputation systems.

No "clean IP" guarantee

The Provider does NOT market or sell its Services as offering "clean", "warm", "fresh", "virgin" or "reputation-screened" IP addresses for email sending, outbound transactional traffic, or any reputation-sensitive use case. All IPv4 and IPv6 addresses are provisioned as-is from the Provider's available pool. The Provider does NOT:

Pre-screen addresses against Spamhaus (SBL, XBL, PBL, CSS, AuthBL, DBL, ZEN), Barracuda Reputation Block List, SORBS, UCEPROTECT (levels 1-3), SpamCop, Cloudmark, Microsoft SNDS / Smart Network Data Services, Google Postmaster Tools, Yahoo Sender Hub, Proofpoint Dynamic Reputation, Cisco Talos, Trend Micro ERS, McAfee TrustedSource, SURBL, Mailspike, PSBL, Invaluement, Hostkarma, Backscatterer, S5H, or any other Real-time Blackhole List (RBL), Domain-based Blackhole List (DBL), URI Blocklist (URIBL), or reputation service before delivery.
Warrant that the assigned address is currently absent from any such list.
Warrant that the assigned address will remain absent from any such list during the Service lifetime.
Provide any contractual remedy, credit, refund or replacement if the address is found listed at any point.

The Client is solely responsible for testing the reputation of any assigned address before relying on it for production workloads, and for taking any appropriate technical measures (multi-IP rotation, third-party SMTP relays, IP warm-up procedures, content filtering, opt-in confirmation flows) to mitigate reputation risk.

Default outbound SMTP (port 25) restriction

To protect the reputation of the Provider's shared IPv4 and IPv6 pools and to limit the use of compromised machines for spam, outbound TCP port 25 (SMTP) is blocked by default on all VPS (LXC) and VDS (KVM) Services. The restriction is enforced at the virtualization firewall, on every network interface of the instance, independently of any firewall rules the Client may configure inside the operating system. This is a standard industry practice: major providers including Amazon Web Services, Google Cloud, Microsoft Azure, DigitalOcean, Vultr, Linode and OVH apply the same default block on outbound port 25.

The restriction applies only to direct server-to-server SMTP relay on port 25. Authenticated mail submission remains available on the standard submission ports (587 with STARTTLS and 465 with implicit TLS), so the Client may continue to send legitimate email through an authenticated mail provider or relay.

Conditional unblocking of port 25

The Provider may, at its sole and absolute discretion, lift the outbound port 25 restriction on a specific Service. Unblocking is never automatic and is never a right attached to the Service. A request will be considered only where all of the following conditions are met:

The Client has completed identity verification (KYC) and the account is fully verified, in good standing, with no outstanding balance and no open or recent abuse case.
The account meets a minimum age and payment-history threshold as determined by the Provider (typically at least 30 days and one settled invoice).
The Client submits a written, specific and verifiable justification describing the mail system to be operated: the application or software used, the nature and source of the recipient lists (with verifiable opt-in), the expected daily volume, and the responsible technical contact.
The Client has correctly configured, and undertakes to maintain, valid reverse DNS (PTR) matching the HELO/EHLO hostname, together with SPF, DKIM and DMARC records for the sending domain.
The Client expressly accepts full responsibility for the resulting outbound traffic and for the reputation consequences described in this Section, including the suspension and no-refund provisions below.

The Provider may decline any request without stating a reason, may grant the unblock for a limited trial volume before any wider release, and may re-impose the block immediately and without notice if abuse, spam, blacklisting, or a single substantiated complaint is associated with the Service. Generic, vague or unverifiable requests (for example "I need to send newsletters", "for my website", "for transactional email") will be declined. The Provider is under no obligation to unblock port 25 for any Client. The inability to send direct SMTP does not constitute a service defect, does not entitle the Client to any refund, credit or service extension, and is not grounds for any claim.

Third-party reputation services are independent of the Provider

Spamhaus, Barracuda, SORBS, UCEPROTECT, SpamCop, Cloudmark, Microsoft, Google, Yahoo, Yandex, Proofpoint, Cisco/Talos, Trend Micro, McAfee, Mailspike and all other reputation-list operators are independent third parties with whom the Provider has no contractual relationship and over whom the Provider exercises no control. The Provider:

Has no influence whatsoever over their listing or delisting decisions.
Will NOT contact these operators on behalf of the Client to request delisting.
Will NOT submit delisting forms, appeals, or attestations on the Client's behalf.
Will NOT pay any "expedited removal" fees charged by these operators (UCEPROTECT and certain others charge for removal).
Will NOT mediate communication between the Client and the reputation operator.
Will NOT issue letters of attestation, source-of-traffic verifications, or compliance certificates to third parties for delisting purposes.

Delisting from any RBL/DBL/URIBL/reputation service is the exclusive responsibility of the Client. The Client is the party with operational knowledge of the workload and must follow the listing operator's published delisting procedure directly.

Client responsibilities

The Client shall:

Test the reputation of any assigned address before deploying production workloads. Recommended tools include MXToolBox, MultiRBL.valli.org, HetrixTools, Spamhaus IP and Domain Lookup, Sender Score, Talos Reputation Lookup, Mail-Tester, and the listing operators' own self-check pages.
Configure proper outbound email authentication for any mail-sending workload: correct reverse DNS (PTR matching the HELO/EHLO hostname), SPF, DKIM, DMARC, valid From / Return-Path domain alignment, TLS for SMTP submission.
Apply gradual IP warm-up for any new outbound mail server, starting with low volumes (typically under 50 messages/day to any single mailbox provider) and ramping up over weeks, not hours.
Monitor outbound traffic for signs of compromise, including hijacked email accounts, infected web applications, vulnerable contact forms, open SMTP relays, or compromised SaaS keys leaking outbound flows.
Respond to abuse reports addressed to the Client's own abuse-c contact (or to the Provider's abuse-c when the Client has not set up its own) within 24 hours.
Take immediate remediation steps when a listing occurs: identify the root cause, stop the offending traffic, follow the listing operator's published delisting procedure, and document the remediation for the Provider on request.
Subscribe to feedback loops (Microsoft JMRP, Google Postmaster, Yahoo CFL, Comcast FBL, AOL FBL, Apple FBL) for any production mail-sending workload to detect complaints early.

Events that trigger suspension or termination without refund

Without limiting the more general Acceptable Use Policy in Section 6, the following IP-reputation events trigger immediate suspension or termination of the affected Services at the Provider's sole discretion, with no refund of any kind:

The Client's address is listed on Spamhaus SBL, XBL, CSS, AuthBL or DBL within 30 days following its allocation, where the Provider determines the listing is attributable to Client activity rather than legacy reputation of the address.
The Client's address receives three (3) or more independent abuse complaints from unrelated sources within a rolling 7-day window, regardless of the listing operator involved.
The Client's address appears on two (2) or more major reputation lists (Spamhaus, Barracuda BBL, SpamCop, UCEPROTECT, Microsoft, Google Postmaster, Proofpoint, Cisco Talos) within a rolling 30-day window.
The Client operates a service that is itself a recognised abuse vehicle: open SMTP relays, mass-mailing systems without verifiable opt-in compliance, "list-rental" platforms, traffic-spinning, fake-engagement, click-farming or comment-spam services.
The Client fails to respond to a Provider-issued abuse notice within 24 hours, regardless of merit.
The Client provides false or misleading information about the intended use of the address (for example: declared use "only internal traffic" or "only website hosting", actual use bulk outbound mail).
The Client circumvents an abuse-related restriction by rotating to a new IP address from the Provider's pool or by re-ordering the Service from a different account.

Scope of suspension: the affected IP address(es), the Service(s) bound to those addresses, and, where the abuse is severe or recurs across multiple IPs/services, the Client's entire account and all related services.

No refund for IP reputation issues, period

The Client expressly acknowledges and accepts that the following situations do NOT entitle the Client to any refund, credit, partial refund, prorated refund, service extension, complimentary IP swap, or any other compensation:

The assigned IP address is found listed on any RBL, DBL, URIBL, reputation service, or sender-reputation database at the time of delivery or at any point thereafter.
The assigned IP address becomes listed during the Service lifetime, regardless of cause, including listings caused by the Client's own activity or third-party activity beyond the Provider's control.
The Client's ability to send email is impacted by reputation listings (failed deliveries, soft bounces, hard bounces, deferrals, quarantines, junk-folder placement, content filtering).
The Client cannot complete delisting through the listing operator's procedure within the Client's preferred or business-required timeframe.
The Service is suspended or terminated for any of the events listed in the previous subsection.
Outbound traffic from the IP is filtered, throttled, dropped, quarantined, or null-routed by third-party networks (mailbox providers, ISPs, transit providers, peers) for reputation, content, or behavioural reasons.
The Client is unable to use the IP address for the specific purpose the Client had in mind at the time of ordering, where the Provider did not expressly warrant suitability for that purpose in the order documentation.

The Services are sold for IP connectivity, computing and storage capacity. They are not sold for email deliverability, sender reputation, or compatibility with any specific third-party filter. The price paid does not include any warranty, implicit or explicit, of address reputation, deliverability rate, inbox placement, or absence from any reputation database.

No IP address swaps for reputation reasons

The Provider does NOT offer IP address swaps, replacements, exchanges or rotations for reputation, deliverability or blacklisting concerns, regardless of who or what is responsible for the listing. This is an absolute rule and applies to all of the following scenarios:

IP addresses that were listed before delivery to the Client (legacy reputation pre-existing on the address).
IP addresses that become listed during the Service lifetime due to Client activity.
IP addresses that become listed during the Service lifetime due to third-party activity beyond the Client's or the Provider's control.
IP addresses listed on Spamhaus, Barracuda, SORBS, UCEPROTECT, SpamCop or any other reputation list, public or private.
IP addresses whose reputation is questioned, scored low, or filtered by any specific mailbox provider, ISP, security gateway or third party.

The Provider's IPv4 and IPv6 pools are shared resources sourced from the Provider's own RIPE NCC allocation. The Provider cannot and does not guarantee that any replacement address would be "clean" or absent from third-party reputation lists. Granting swaps would simply transfer the same reputation risk to another Client, without any technical or commercial benefit. The Provider often does not have clean alternative addresses available in its pool, and it has no obligation to acquire any.

Clients with reputation-sensitive workloads (outbound email, transactional notifications, marketing newsletters, OTP/2FA delivery) must:

Test the IP reputation before deploying production traffic, using the tools listed in the "Client responsibilities" subsection above.
Use a dedicated transactional email service for mail sending (see "Recommended approach for reputation-sensitive workloads" below).
Accept that the IP address delivered is the IP address delivered, with no exchange, no swap, no replacement and no refund possible based on its reputation, at any time during the Service lifetime.

Any request for IP address replacement on reputation, deliverability or blacklisting grounds will be politely declined. This rule is not negotiable, not subject to commercial appeal, and not waivable by Provider sales or support staff.

Recommended approach for reputation-sensitive workloads

For Clients whose business outcomes depend on outbound email deliverability (transactional mail, marketing newsletters, billing notifications, OTP/2FA delivery, password resets, customer notifications), the Provider strongly recommends using a dedicated transactional email service: SendGrid, Postmark, Mailgun, Amazon SES, Mailjet, SparkPost, Resend, Sendinblue/Brevo, Mandrill, Postal hosted, or equivalent. These services maintain professionally warmed reputation pools, handle bounce and complaint feedback loops, provide deliverability tooling and dashboards, and operate at a scale that no individual IP can match.

The Provider does not operate such a service and does not represent its allocated IPs as a substitute for one. Clients who choose to send email directly from the Provider's IPs do so at their own risk and accept full responsibility for the resulting deliverability outcome.

Limitation of liability for reputation issues

To the maximum extent permitted by Romanian and European Union law, the Provider is NOT liable for any of the following, whether the loss is direct, indirect, consequential, incidental, special, or otherwise:

Email that fails to deliver, is delayed, is deferred, is filtered, or is placed in a junk/spam folder due to IP, domain, content, or behavioural filtering by any third party.
Lost business, lost contracts, lost revenue, lost opportunity, customer churn, or damage to the Client's commercial reputation resulting from IP listings or filtering.
Time, cost, or effort spent by the Client interacting with reputation operators for delisting, including any fees charged by those operators.
Decisions taken by third-party operators (mailbox providers, RBL/DBL operators, ISPs, transit providers, antivirus vendors, security gateways) to block, throttle, quarantine, filter, or score traffic originating from the assigned address.
Any consequential, indirect, incidental, special or punitive damages related in any way to reputation listings or filtering.

This clause is to be read in conjunction with Section 23 (Limitation of Liability). In the event of any inconsistency between this subsection and Section 23, the broader limitation applies in favour of the Provider.

19. DSIX Internet Exchange

The DreamServer Internet Exchange (DSIX), operated under AS58218, is a peering platform hosted in the Provider's Bucharest Datacenter. DSIX offers free Layer 2 peering to eligible members connected to the Provider's services.

Eligibility

Member must operate a public ASN and have a PeeringDB record maintained up to date.
Member must be a Client of the Provider holding at least one Dedicated Server or Virtual Server plan, unless under a separate DSIX-only agreement.
Member must comply with the DSIX policies, the Route Server filter policy, and the MANRS guidelines (appropriate prefix filtering, RPKI/IRR validation, anti-spoofing).

Technical requirements

Dual-stack (IPv4 and IPv6) strongly encouraged.
Members must not announce default routes, private ASNs, martians, or unassigned prefixes to the Exchange.
Members must not announce prefixes for which they are not the legitimate origin AS (no BGP hijacking, no route leaks).
AS112 queries must be handled locally by the Exchange AS112 infrastructure and must not be announced by members.
All peering is via the DSIX Route Servers by default. Bilateral peering is permitted and encouraged between members.

Port speeds & cost

Both 1 Gbps and 10 Gbps ports are available at no cost for DreamServer Service Clients, subject to port availability. A port upgrade from 1 Gbps to 10 Gbps is performed within 24 hours of approval, at no charge. There is no monthly fee, no setup fee, and no bandwidth cap on peering traffic.

Abuse & disconnection

The Provider reserves the right to immediately disconnect any DSIX member for: repeated route leaks; BGP hijacking (intentional or accidental); announcing prefixes without authorization; transit leaks (using DSIX for full transit without agreement); repeated non-response to operational or abuse communications; or any other violation of the DSIX policy or these Terms.

20. Domain Registration

Domain registration services are provided by the Provider acting as an accredited registrar with RoTLD (for .ro domains) and through partner registries for other TLDs. The following conditions apply:

Domain registrations are subject to the policies and regulations of the applicable registry (RoTLD, ICANN, EURid, or other relevant bodies).
The Provider registers domains on behalf of and in the name of the Client. The Client is the legal registrant of the domain.
The Client is solely responsible for any disputes arising from domain registration, including UDRP proceedings and trademark conflicts.
The Client is responsible for ensuring timely renewal of domains. The Provider will send renewal reminders but bears no liability for domains that expire due to the Client's failure to renew.
Domain registration fees are non-refundable once the registration or renewal has been processed by the registry.
Transfers in/out of domains follow the applicable registry policy (EPP auth code for transfer-out, domain unlocking, 60-day transfer lock after registration for gTLDs, etc.).
Expired domains enter a grace period (typically 30 days) during which the Client may redeem the domain subject to a redemption fee set by the registry.

.RO Domains

The Provider defines the domain name registration service as the procedure through which the Provider registers domain names in the name of its Clients, in accordance with the provisions of the top-level authority "INSTITUTUL NATIONAL DE CERCETARE-DEZVOLTARE IN INFORMATICA" (ROTLD). Purchase, renewal, and transfer of domain names are subject to the top-level registrar's contract and are fully accepted by the Client. The contractual clauses to be respected by the Client are published at www.rotld.ro, in the sections "Contract pentru Inregistrare" and "Reguli de Inregistrare".

Note: the top-level authority has announced the future introduction of an annual domain name maintenance fee for .ro domains. When this fee is introduced, the applicable terms and conditions will be published on www.rotld.ro and will automatically apply to the Client's .ro domains registered through the Provider.

Domain Name Service (all TLDs)

The Domain Name Service represents the registration and renewal of domain names and the right of use by the Client of the chosen domain name, in accordance with the Provider's offer and the terms and conditions of the top-level registrar. The respective terms and conditions are published on the top-level registrar's website. Examples:

Generic TLDs (.com, .net, .org, etc.): icann.org/policy
.eu domains: eurid.eu rules for .eu
.ro domains: rotld.ro

By ordering or renewing a domain name through the Provider, the Client confirms that they have read and agree to the applicable registry terms and conditions.

21. Reseller Services

Reseller access is offered under a separate Reseller Agreement which supplements these Terms. Key provisions include:

White-label billing: the Reseller bills its own customers directly and is the customer of record for the Provider.
Primary support: the Reseller is responsible for first-line support to its own customers. The Provider provides infrastructure and escalation-only support to the Reseller.
AUP compliance: the Reseller remains responsible under these Terms for all traffic, content, and conduct originating from its customers.
Payment terms: reseller invoices may use different billing cycles or credit arrangements as set in the individual agreement.
Termination: breach of AUP by a reseller's customer may result in suspension of the underlying reseller services if not remedied; the Reseller remains jointly responsible.

22. Intellectual Property

The Client retains all intellectual property rights in the content, data, and software stored on or transmitted through the Provider's infrastructure.

The Provider retains all intellectual property rights in its infrastructure, network, software, systems, trademarks, logos, website content, and proprietary tools. The Client shall not reverse-engineer, decompile, or disassemble any proprietary software or systems provided by the Provider.

Neither party acquires any intellectual property rights of the other party by virtue of this Agreement unless expressly agreed in writing.

23. Limitation of Liability

The Provider's total aggregate liability for any and all claims arising from the provision of Services shall not exceed the total fees paid by the Client for the affected Service during the three (3) months immediately preceding the event giving rise to the claim.

The Provider shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to loss of profits, loss of data, loss of business opportunities, or loss of goodwill, even if the Provider has been advised of the possibility of such damages.

24. Force Majeure

The Provider shall not be liable for service interruptions or failures caused by force majeure events, including but not limited to: natural disasters (earthquakes, floods, fires), pandemics, power grid failures beyond the Provider's infrastructure, government actions, war, civil unrest, terrorism, cyberattacks of unprecedented scale, failures or maintenance of upstream telecommunications providers, or disruptions of public internet routing outside the Provider's control.

During a force majeure event, the Provider will use commercially reasonable efforts to minimize the impact and restore service as soon as possible.

25. Suspension & Termination

Suspension by the Provider

The Provider may suspend Services immediately and without prior notice in the following circumstances:

Violation of the Acceptable Use Policy (Article 6).
Non-payment exceeding 14 days past the invoice due date (Article 5).
Receipt of a valid legal order requiring suspension.
Activities that pose an imminent risk to the Provider's infrastructure or to other clients.
RIPE policy violation or IP resource abuse (Article 17).
DSIX policy violation (Article 18).

Termination by the Client

The Client may cancel any Service by providing at least 30 days written notice via the client area or by email to contact@dreamserver.ro. Cancellation takes effect at the end of the current billing period.

Termination by the Provider

The Provider may terminate Services immediately in cases of material breach, including repeated AUP violations or non-payment exceeding 30 days. In such cases, no refund will be issued.

Technical limitations and unilateral termination for damage to the Provider

The Provider reserves the right to apply technical limitations to the contracted service and/or to unilaterally terminate this Agreement with immediate effect, in exceptional circumstances, if direct or indirect damage of any kind is caused to the Provider by the Client or by the manner in which the contracted Services are used. In such cases, no refund will be issued and the Provider may pursue compensation for the damage caused.

Restrictions during a third-party lawsuit

If a judicial process is pending against a Client, brought by a third party alleging that information or files published on the internet using the Provider's infrastructure infringe the legal rights of the claimant, and if the Provider considers that there are reasonable grounds for a legal interpretation supporting the legitimacy of the third party's claim, the Provider reserves the unilateral right to impose restrictions on the Client's contracted services for the duration of the judicial process, in order to limit potential harm to the claimant, to the Provider, or to other Clients.

Data retention after termination

Upon termination, the Client has 7 calendar days to retrieve their data by restoring their service. After this period, the Provider will permanently and securely delete all Client data from its systems.

26. Refund Policy

Setup fees: non-refundable once the service has been provisioned.
Monthly billing: no refund is issued for the remaining unused portion of the current month.
Yearly billing (Micro Servers and yearly-discounted plans): the Client is entitled to a pro-rata refund for the remaining full months, minus any applicable setup fees and non-refundable charges.
Domain registrations: non-refundable once registered or renewed.
LIR services: annual fees are non-refundable once the sponsorship period has started.
Satisfaction guarantee: new Clients on standard configurations may request a full refund of the first month's fee within 7 days of service delivery if the service does not meet expectations. This applies only once per Client and not to custom configurations or managed services.

27. Governing Law & Disputes

This Agreement is governed by and construed in accordance with the laws of Romania.

Any dispute arising from or in connection with this Agreement shall first be subject to amicable resolution through good-faith negotiation between the parties for a period of 30 calendar days from the date of written notification of the dispute.

If no resolution is reached within the amicable period, the dispute shall be submitted to the exclusive jurisdiction of the competent courts of Bucharest, Sector 1, Romania.

Consumer clients in Romania may also use alternative dispute resolution bodies such as ANPC SAL or the EU Online Dispute Resolution platform ec.europa.eu/consumers/odr.

28. Modifications

Given the rapid pace of technological and legislative change, and taking into account the individual and collective needs of Clients, the Provider, at its sole discretion, may modify or amend any clause of this Agreement, as well as any policies or conventions included in or referenced by this Agreement, at any time.

Such modifications or additions enter into force 15 days after publication on dreamserver.ro, with the exception of the "Terms and Conditions" section itself, which enters into force immediately upon publication on the Site.

Continued use of the Site or Services after such modification or addition constitutes your express acceptance of the clauses of the Revised Agreement. If you do not wish to give your acceptance and do not agree with the Revised Agreement, you may stop using the Site or the Services and terminate the affected services in accordance with Article 24.

The Provider will notify the Client by email about material changes to this Agreement and accepts no responsibility if such notifications do not reach the Client as a result of an incorrect email address provided by the Client, or any other circumstance outside the Provider's control that may influence communication between the Provider and the Client.

29. Final Provisions

Severability. If any provision of this Agreement is held to be invalid, illegal, or unenforceable, the remaining provisions shall continue in full force and effect.
Entire Agreement. This Agreement, together with the SLA, Privacy Policy, and any applicable order forms or addenda, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior agreements, representations, and understandings.
Assignment. The Client may not assign or transfer this Agreement or any rights hereunder without the prior written consent of the Provider. The Provider may assign this Agreement to a successor entity in connection with a merger, acquisition, or sale of substantially all of its assets, upon written notice to the Client.
Waiver. The failure of either party to enforce any provision of this Agreement shall not constitute a waiver of that party's right to enforce that provision or any other provision in the future.
Notices. All notices under this Agreement are valid when sent by email to the address registered in the Client's account (Client) or to contact@dreamserver.ro (Provider).
Language. These Terms are published in English and Romanian. In case of conflict between the two versions, the Romanian version prevails for Romanian consumers and for any dispute brought before a Romanian court; the English version prevails for international business clients.

30. Contact

For inquiries related to these Terms and Conditions, billing, or general matters:

General: contact@dreamserver.ro
Technical / NOC: noc@dreamserver.ro
Abuse reports: abuse@dreamserver.ro
Phone: +40 773 870 363

Postal address: S.C. DreamServer S.R.L., Str. Mircea Vulcanescu, Nr. 2, Et. 7, Ap. 25, Sector 1, Bucharest, Romania.

Last updated: June 2026.

1. Definitions

2. Scope of Services

3. Account Registration & Client Obligations

4. Orders, Activation & Service Delivery

5. Pricing, Payment & Billing

6. Acceptable Use Policy

7. Fair Use & Resource Limits

8. Data Protection (GDPR)

9. SLA & Uptime

10. Backups & Data Responsibility

11. Dedicated Servers (Blade, Enterprise, Game, Micro)

12. Virtual Servers (VPS LXC & VDS KVM)

13. Remote Management & OS Installation

14. Hardware Upgrades & Modifications

15. Loyalty Gift Program

16. RTBH DDoS Mitigation

17. IP Resources & LIR Services

18. IP Reputation, Anti-Spam & Blacklists

19. DSIX Internet Exchange

20. Domain Registration

21. Reseller Services

22. Intellectual Property

23. Limitation of Liability

24. Force Majeure

25. Suspension & Termination

26. Refund Policy

27. Governing Law & Disputes

28. Modifications

29. Final Provisions

30. Contact

Trusted By & Member Of