2022+ CPUs, DDR5, NVMe · No KYC · Pay in crypto: BTC, USDT, USDC, ETH, SOL, LTC
Language: English
Order bare metal

Legal · Effective 1 November 2026

Acceptable Use Policy

What an Lumenfer dedicated server may run, the ten prohibited uses one by one, what the abuse desk does with a report, and how a suspension is appealed.

Last updated: · 6 min read

Quick answer

Which uses does Lumenfer allow on a dedicated server?

Lumenfer dedicated servers may host websites, a self-run VPN, Tor relays (exits included), Proxmox VE virtual machines, game servers and Bitcoin or Monero full nodes. DMCA notices get no action, because only Panamanian law and Panamanian courts apply. The banned list has ten items: spam, phishing, malware and botnets, attacks, scanning, booters, carding and fraud, child sexual abuse material, mining, and serving sanctioned people. Outbound port 25 stays closed, and breaches mean suspension.

1. Scope

This policy covers every Lumenfer account and dedicated server, every virtual machine running on one, and every person who uses them. It belongs to the Lumenfer terms of service and applies whatever plan from the pricing page you rent. You answer for what runs on your server, including the machines and logins you hand to other people.

2. Which law applies?

Lumenfer is operated by DomaineGoat LLC, registered in Panama, and is bound only by Panamanian law. Each datacenter sits in its own country and is subject to that country’s law. Lumenfer takes no action on a legal demand that rests on the law of another country.

3. What may run on a server?

Anything that section 6 does not prohibit may run on your server. Uses Lumenfer names as allowed:

  • websites, web applications, APIs and self-hosted services;
  • your own VPN with WireGuard or OpenVPN (see should I use a dedicated server for my own VPN);
  • Tor relays of every kind (section 4);
  • virtual machines under Proxmox VE (see how do I install Proxmox on a dedicated server);
  • game servers (see can I host game servers on a rented dedicated server);
  • full Bitcoin or Monero nodes (see can I run a Bitcoin or Monero node on a dedicated server);
  • language models on the processor (see can I run an LLM on a dedicated server without a GPU);
  • a mail server whose outgoing mail is relayed by a provider on port 465 or 587 (section 7);
  • storage, backups, development and test machines.

4. Are Tor relays allowed?

Yes. Tor relays of every kind are permitted: exit relays, middle relays and bridges. Since every server has outbound port 25 shut, an exit relay cannot carry SMTP traffic on that port.

The guide on running a Tor exit relay on a dedicated server covers the setup. The legal side is in is it legal to run a Tor exit node.

DMCA notices and other foreign copyright notices are not acted on: only Panamanian law and orders of Panamanian courts bind us. Notices filed under the DMCA, or under the copyright law of any other foreign state, trigger neither a takedown nor a suspension.

The prohibited uses of section 6 stay in force on every server, whatever happens to copyright notices. For the reasoning, read what does "DMCA ignored" mean for a dedicated server: it treats the rule as a matter of jurisdiction.

6. Which uses are prohibited?

Not allowed: spam or bulk email, phishing, malware or botnet control, DDoS or any other attack, scanning or brute-forcing systems you do not own, booter or stresser services, carding or fraud, child sexual abuse material, cryptocurrency mining, and serving sanctioned people or companies.

The table spells out each of the ten items. Each one applies to the server itself, to every virtual machine on it and to any service you sell from it.

Prohibited useWhat it covers
Spam or bulk emailUnsolicited messages and mass mailings to people who did not ask for them, on any port and through any mail provider.
PhishingPages, messages or apps that pose as a bank, a wallet, a shop or any other service to collect logins, card details or recovery phrases.
Malware or botnet controlHosting or spreading malicious software, and running the command-and-control servers that steer infected machines.
DDoS or other attacksFloods, exploit traffic or any attack sent from the server, or from a machine on it, against any system.
Scanning or brute-forcingPort scans, vulnerability scans and password guessing aimed at systems that belong to other people.
Booter or stresser servicesRunning or selling a service that floods targets on demand, whatever name it uses, "stress testing" included.
Carding or fraudTesting or using stolen card data, fake shops, scam pages and any other scheme to take money or goods by deceit.
Child sexual abuse materialAny such material, in any form, stored, shared or linked. There is no exception.
Cryptocurrency miningMining any coin with any software, on the server or inside a virtual machine on it.
Service to sanctioned people or companiesAny account or service for a person or a company on a sanctions list, or in a country or region that section 8 names.

Three points mark where each rule stops:

  • Mining and nodes: a full node checks a blockchain and mines nothing, so a Bitcoin or Monero node is allowed.
  • Scanning: you may scan and test machines you own; machines owned by others are off limits.
  • Email: personal and business mail from your own mail server is fine once a provider relays it on port 465 or 587. Mass mailing stays banned whatever the port or provider.

7. Why is port 25 closed?

Outbound SMTP on port 25 is blocked on every server and is never unblocked; submission ports 465 and 587 to mail providers remain open. A mail server on Lumenfer therefore relays its outgoing mail through a provider on 465 or 587. Setup details: can I host a mail server on an offshore dedicated server.

8. Who cannot use Lumenfer?

People and companies in Cuba, Iran, North Korea, Syria, Russia, Belarus, China, Yemen, Western Sahara or the occupied regions of Ukraine cannot be served. Every incoming payment is screened against public sanctions lists of blockchain addresses, and a payment from a listed address is not credited. You must be 18 or older to open an account.

9. How are abuse reports handled?

Foreign copyright and DMCA notices get no action; Panamanian law and Panamanian court orders do. Spam, phishing, malware, botnet control, attacks and child sexual abuse material are forbidden and get the server suspended.

Reports about any Lumenfer IP address belong at [email protected]. The team acts faster on a report that gives:

  • which Lumenfer IP address is involved;
  • when the activity took place, in UTC if possible, or with the time zone stated;
  • what kind of abuse it is, for example spam, phishing, malware, an attack or a scan;
  • proof such as logs, full email headers or the offending URL.

The abuse desk takes no action on copyright complaints, whether they cite the DMCA or another foreign law.

10. What does a suspension mean?

A breach of section 6 leads to suspension. Your dashboard marks the server as suspended; email support to learn the reason. A server suspended for a breach earns no credit for its remaining days, since the refund policy grants credits only in its own listed cases.

Running out of paid days is different. The terms of service set out that suspension: the disks are kept for 7 days, then wiped.

11. How do I appeal a suspension?

Email [email protected]. A person answers support emails within 12 hours, seven days a week, including help with SSH keys, RAID, reinstalls and firewall rules.

  • State the server's order reference (ORD-…) and its IP address.
  • Leave your account number out of the message. Nobody from our team will ever ask for your account number, your root password or your private SSH key, by email or in a chat.
  • Explain what happened and what you changed, such as the malware you removed, the open mail relay you closed or the virtual machine you shut down.

12. When are records handed over?

Records go out only when a Panamanian court orders it. Each record that exists appears in the privacy policy. No logs are kept: no connection logs, no traffic logs and no visitor or customer IP addresses, on the site, in the dashboard or on the servers.

13. Changes to this policy

This version of the policy is dated 1 November 2026. We can update it. The version in force carries the date shown at the top, and changes reach every server from that date.