FAQ

Who can join the xHOSTING community?

Short answer: users registering with a valid invitation can order immediately; users registering without an invitation need an approved access request before ordering.

In detail: xHOSTING is a controlled-access, community-based system. Users registering with a valid invitation may order without a separate request. Users registering publicly without an invitation can create an account, but ordering is not possible until they submit an access request and it is approved either automatically or after administrator review. The goal remains to preserve the quality, security, and sustainability of the community.

How can someone register and request access?

If you have a valid invitation, register with it and you will receive ordering rights immediately, without a separate access request.

If you do not have an invitation, you can still register publicly in the client area. In that case, the account is created, but ordering services requires an access request. Based on its content, the automated system may approve it, reject it, or forward it for further administrator review.

Who is authorized to send invitations?

Only xHOSTING members with the appropriate permissions may send invitations.

The right to invite is not a default right; it is tied to a specific status and community conditions. Whether a member has active invitation rights depends on the conditions defined in the community policy and on decisions made by the xHOSTING operators.

Is there a limit on how many invitations a member can send?

Yes, the number of invitations is limited.

An eligible member may use a defined number of invitations, which is currently: 1 invitation. Invitation rights are not cumulative, do not renew automatically, and each invitation is permanently consumed once accepted. The purpose of this limitation is to protect resources and prevent overselling.

What responsibility is associated with issuing an invitation?

Issuing an invitation carries responsibility.

The inviting member assumes responsibility for ensuring that the invited person becomes familiar with and complies with xHOSTING rules, especially the Code of Conduct and the Acceptable Use Policy (AUP). In cases of repeated or serious abuse, invitation rights may be restricted or revoked.

What happens if an invited member violates the rules?

In the event of a violation, xHOSTING will take action depending on the severity of the case.

This may include a warning (WARN), service restrictions, or even termination of membership. In cases of serious or repeated violations, the invitation rights or membership of the inviting member may also be affected.

Can an invitation be revoked or expire?

Yes, invitations can be revoked and may have limited validity.

xHOSTING reserves the right to revoke an invitation for technical, security, or community-related reasons. Unused invitations may expire or become invalid if the inviting member loses their invitation rights.

Can an invitation be sold or transferred?

No. Invitations may neither be sold nor transferred.

An invitation applies exclusively to the person for whom it was originally intended by the authorized member. Selling, exchanging, or transferring invitations to third parties constitutes a serious violation and may result in immediate sanctions.

Why is xHOSTING a controlled-access system?

The controlled-access model protects the quality, security, and sustainability of the community.

Open registration does not mean that anyone can automatically order services. A valid invitation grants immediate ordering rights; without an invitation, the access request helps keep community size and resource usage controlled, while reducing the risk of abuse, overload, and legal issues.

How does xHOSTING differ from a traditional hosting provider?

xHOSTING is not a classic hosting provider but a community-based technical infrastructure.

There is no public package offering, SLA, customer support prioritization, or guaranteed availability. The system does not operate on a commercial basis but relies on community contributions and voluntary operation.

Is xHOSTING considered a commercial service?

No, xHOSTING is a community initiative, not a commercial hosting service.

Community (free) services are not considered commercial hosting or electronic communications services. Certain separate services (such as domain registration) may be available as fee-based services under a separate legal relationship.

Is payment required to join or maintain membership?

No, membership itself is not subject to a fee.

The operation of xHOSTING is supported by voluntary community contributions. These do not constitute purchases or subscriptions and do not grant automatic rights or guarantees.

What does “community-based operation” mean in practice?

Community-based operation means that xHOSTING does not function as a customer–service provider relationship.

Members jointly contribute to maintaining the system, comply with community rules, and use resources responsibly. The emphasis is on trust, cooperation, and sustainability.

What does a member receive in return for community membership?

Members gain access to the xHOSTING community infrastructure.

This may include web hosting, email services, databases, SSH access, and the xHOSTING Control Panel (XCP). Exact features depend on current resource capacity and configuration.

In what cases can membership be terminated?

Membership may be terminated due to rule violations, abuse, or a community decision.

Serious or repeated breaches of rules, violations of the AUP, or behavior that endangers community operation may result in termination of membership.

Can membership be voluntarily terminated?

Yes, membership can be terminated voluntarily at any time.

A member may request account closure, after which access to community (free) services will cease. Termination does not entail obligations or sanctions.

What happens to services when membership ends?

Access to community services is terminated.

After termination, xHOSTING may retain data for a limited period for technical purposes, after which it will be permanently deleted. Fee-based services (such as domain services) may remain available under a separate legal relationship.

Where can xHOSTING rules and policies be found?

xHOSTING rules and policies are publicly available on the official website.

These include in particular the Policy, the Acceptable Use Policy (AUP), the Privacy Policy, and the Cookie Policy. These documents are accessible before joining and throughout the entire membership period and form the basis of community membership.

What conduct does xHOSTING expect from its members?

xHOSTING expects polite, respectful, and trust-based behavior from its members.

Members must comply with the policy, respect others’ resources and rights, and refrain from any activity that could endanger the operation, reputation, or security of the community.

What is a WARN, and when is it applied?

A WARN is an official warning issued by the Operators in cases of rule violations.

A WARN may be issued for violations of the Acceptable Use Policy, behavior that breaches community norms, abuse of resources, or repeated minor infractions. The purpose of a WARN is not punishment, but awareness and protection of the community.

Is there an appeal option for community decisions?

Community decisions are not authority-based or official legal decisions.

The Operators may provide an opportunity for discussion or consultation; however, decisions related to membership, moderation, or community operation do not qualify as appealable administrative rulings.

Does community behavior affect future permissions?

Yes, community behavior can directly affect certain permissions.

Compliant and cooperative conduct may be a prerequisite for obtaining or retaining rights such as invitation privileges. In the case of an active WARN, abuse, or repeated rule violations, certain permissions may be restricted or revoked.

What is the purpose of the XBASIC package within xHOSTING?

XBASIC is the internal package name used in the xHOSTING Control Panel (XCP) for the unified free web hosting profile. It is not a paid “Basic” tier and does not imply a “Pro” package level.

Its purpose is to provide a stable, transparent, and sustainable technical foundation for websites, email, and smaller online projects while respecting community principles.

Who is the XBASIC package recommended for?

The XBASIC package is recommended for those seeking reliable but non-commercial hosting.

It is particularly suitable for personal projects, presentation websites, smaller web applications, email usage, learning or development purposes, and for users who accept the principles of community operation and shared resources.

Are there any packages other than XBASIC?

There is currently one unified free web hosting profile; its internal XCP package name is XBASIC.

The name does not represent a paid package hierarchy. A unified profile supports transparent operation, prevents overload, and helps distribute community resources fairly.

Can the XBASIC package be expanded or modified later?

The XBASIC package has fundamentally fixed limits.

Certain permissions or technical options—such as special access—may be enabled upon request on a case-by-case basis, provided they do not endanger community operation. Traditional package upgrades or scaling are not part of the system.

What does it mean that resources operate on a community basis?

The community principle means that xHOSTING infrastructure is shared by members with consideration for one another.

Resources are not guaranteed, isolated capacities but shared technical capabilities. Therefore, members are expected to use services as intended, avoid excessive load, and respect the interests of the community.

What does 25 GiB of storage mean in practice?

The 25 GiB of storage is shared by website files, databases, email accounts, and related data.

The number of websites or applications that fit is not fixed: actual usage depends on the size of files, databases, and email data. The capacity value alone is not an application-compatibility promise.

What does the 10 TiB traffic allowance mean?

The 10 TiB value is the public traffic allowance of the unified web hosting profile.

It does not guarantee bandwidth or a business SLA; actual usage depends on the content served and the resulting traffic.

What happens when the traffic allowance is reached?

The public profile does not define an automatic throttling or suspension rule.

Current handling can be confirmed through the Support system; the documented allowance does not imply unlimited traffic or guaranteed performance.

What happens if I run out of storage?

The unified profile has a storage limit of 25 GiB. Additional data requires free space to be made available first, for example by removing unnecessary files or emails belonging to the account.

The public profile does not define an automatic restriction or suspension rule. Current handling can be confirmed through the Support system.

What types of files can I store on the hosting space?

The hosting space is intended primarily for files required to operate websites, databases, email data, and related content.

Storing content that is illegal, infringes copyright, is harmful (e.g., malware), or unjustifiably burdens community resources is prohibited. Detailed restrictions are defined in the Acceptable Use Policy (AUP).

What does it mean that 5 domains can be used?

Within the unified profile, a Member may use up to 5 separate domain names in total.

These may serve as independent websites or domains with distinct purposes. The limit aims to ensure balanced use of community resources rather than impose artificial restrictions.

Can I use my own domain name on xHOSTING?

Yes. xHOSTING fully supports the use of privately owned domain names.

The domain may be registered elsewhere; in such cases, DNS settings must be pointed to the values provided by xHOSTING. Domain management and DNS editing are available through the xHOSTING Control Panel (XCP).

What does a total of 10 subdomains mean?

A subdomain is a separate address under a main domain, such as blog.example.com or dev.example.com.

The unified web hosting profile allows 10 subdomains in total. This is one shared limit for the complete profile, not an allowance per domain.

Can additional domains be added later?

The unified profile allows 5 domains. This is the documented limit; the public interface does not promise automatic expansion beyond it.

Can I delete or replace my main domain?

Yes. Deleting or replacing the main domain is permitted via XCP.

Before performing the operation, it is the Member’s responsibility to back up associated websites, email accounts, and data. After deletion, related services may cease or require reconfiguration.

What do 10 email accounts and 20 email addresses/aliases mean?

The unified profile allows up to 10 separate email accounts, each with its own mailbox and login.

Email addresses and aliases are a separate limit of 20 in total.

What is the difference between an email account and an email address?

An email account is a technical mailbox with a username, password, and storage.

An email address is a reachable address (e.g., info@domain.com) that points to an email account or forwards messages to other addresses.

Multiple email addresses can be assigned to one email account as aliases; the profile allows 20 email addresses and aliases in total.

Is a catch-all email function available?

Yes. The XBASIC package supports the catch-all function.

Catch-all allows all emails sent to non-existent addresses of a domain to be delivered to a specified email account. This setting can be configured in XCP.

Can email forwards be set up?

Yes. The unified profile allows up to 20 email forwarders.

Forwarding allows emails arriving to an email address to be automatically forwarded to another address (for example, to an external email provider), even without creating a mailbox.

Can an external email client be used (e.g., Outlook, Thunderbird)?

Yes. xHOSTING’s email service is fully compatible with standard email protocols.

Email can be used with external clients (e.g., Outlook, Thunderbird, Apple Mail) via IMAP/POP3 and SMTP. The required server details are available in the XCP interface.

What does the 5-database limit mean?

Within the unified profile, you can create up to 5 databases in XCP.

This limit applies to the number of databases (e.g., site1_db, site2_db, wp_db), not to the number of tables. A database may contain any number of tables, as long as it fits within the storage and resource limits.

Which web applications are compatible with xHOSTING's database environment?

An application can be used safely when its database, PHP, and resource requirements match the current hosting environment and the documented profile limits.

The public profile does not define a specific application catalogue, database engine, or engine version. Before installation, compare the application's requirements with the environment actually available in XCP.

Can a web application or CMS be installed?

Yes, when the application complies with the AUP, the hosting profile's resource limits, and the runtime environment currently available.

Check the application's requirements before installation. Fixed PHP limits include 256M memory_limit and 128M upload_max_filesize; they cannot be changed through a custom php.ini file or in XCP.

Is there an application installer in the xHOSTING Control Panel (XCP)?

Yes. In the XBASIC package, the “Applications” permission is enabled: it provides access to the XCP application installer feature, which can simplify installing several popular web applications.

The exact list of available applications is shown in the XCP and may change over time.

Can I run my own custom application?

Yes. You can also run a custom web application if you comply with xHOSTING rules (especially the AUP) and the application does not place a disproportionate load on community resources.

The XBASIC package supports a typical web stack (FTP, PHP, SSH, database), so custom PHP projects, static sites, and applications running in a controlled environment can be implemented.

What does the 5-FTP-user limit mean?

Within the unified profile, you can create up to 5 separate FTP users in XCP.

Each FTP user has their own username and password, and can be used separately to upload, modify, or delete files. This is useful, for example, if you want to separate multiple websites, subdomains, or developers.

Is there a browser-based file manager available?

Yes. XCP includes a browser-based file manager.

The file manager allows, among other things:

• uploading and downloading files,
• creating and deleting directories,
• editing files (e.g., configuration files),
• basic permission management.

This is especially useful if you want to make a quick change without using an FTP client.

Can SFTP or an encrypted connection be used?

Yes. In the xHOSTING environment, an encrypted connection can also be used to access files.

If SSH is enabled for your account, FTP users can also connect via SFTP, which uses the SSH protocol, so the traffic is encrypted.

This is a recommended solution on public networks and when handling sensitive data.

Can FTP user permissions be restricted?

An FTP user's actual directory scope depends on the current XCP settings, so verify exactly which files the account can access when it is created.

The public profile defines the number of FTP users but does not promise a specific isolation technology or an identical permissions model in every environment.

Which PHP versions are available?

The PHP version can be selected per domain in the xHOSTING Control Panel (XCP).

Actively updated branches; the latest stable patch release in each branch is available:

• PHP 8.5
• PHP 8.4
• PHP 8.3
• PHP 8.2

Fixed legacy versions available for compatibility:

• PHP 8.1.34
• PHP 8.0.30
• PHP 7.4.33
• PHP 7.3.33
• PHP 7.2.34
• PHP 7.1.33
• PHP 7.0.33
• PHP 5.6.40

Legacy versions are not recommended for new projects. ionCube Loader is available for PHP versions for which an official stable ionCube Loader release is available.

Can PHP settings be modified (memory_limit, upload size, etc.)?

No. The following four PHP resource limits are centrally fixed:

• memory_limit: 256M
• max_execution_time: 180 seconds
• post_max_size: 128M
• upload_max_filesize: 128M

They cannot be changed through a custom php.ini file or in XCP. Per-domain PHP version selection is a separate feature.

What does displaying open_basedir and disable_functions mean?

open_basedir can restrict the directories available to PHP scripts, while disable_functions can be used to disable specified PHP functions.

The public profile does not define the exact value, scope, or XCP display of these settings. Always compare an application's requirements with the actual configuration of the current PHP environment.

What does the PHP-FPM operating mode mean?

ondemand pm is the centrally configured PHP-FPM (Process Manager) operating mode.

In this mode:

• PHP processes are started only when an actual request arrives,
• they do not consume resources while idle,
• it provides more efficient memory usage in a community environment.

This mode is especially suitable for low to medium traffic websites and fits well with xHOSTING’s sustainable resource management principles.

What do the pm.max_children and pm.max_requests values mean?

These are centrally fixed, server-side parameters that control PHP-FPM operation; users cannot change them.

pm.max_children:

• defines how many PHP processes can run simultaneously,
• in the unified profile this value is: 3,
• this protects the system from overload.

pm.max_requests:

• specifies after how many requests a PHP process should be restarted,
• in the unified profile: 1000,
• helps prevent issues caused by memory leaks.

These values ensure a balance between stability, performance, and community resource usage.

Is SSH access included in the XBASIC package?

Yes. The unified web hosting profile provides a limited SSH environment for hosting-related command-line tasks.

This is not full system-level access. Available commands and capabilities must be checked in the current hosting environment.

What does a restricted SSH environment mean?

A limited SSH environment provides hosting-related command-line access, but it does not mean full system-level privileges.

The public profile does not promise a specific isolation technology or permanent command set. Check the required tool in the current environment before relying on it.

Can I run my own commands via SSH?

You can run hosting-related commands that are actually available in the limited SSH environment.

The public profile does not guarantee any particular development tool or command. Check current capabilities first and limit operations to your own hosting service.

Can remote database access be granted in specific cases?

In short: remote database connections are unavailable by default and TCP port 3306 is closed.

An exception may be enabled only after an individually reviewed request submitted through the Support system with a detailed technical justification and, if approved, only for 1 specified source IP address.

Can an individual permission be requested for database access?

Yes, but remote access is not a default package feature. The request must be submitted through the Support system with a detailed technical justification.

Access is not automatic: it requires individual approval and, if approved, is limited to 1 specified source IP address.

Is a backup capability available?

Yes. A backup capability is part of the unified web hosting profile.

The public profile does not promise a specific frequency, retention period, or guaranteed restore. Always keep a separate, verified copy of important data.

Where can the available backup options be checked?

Check the currently available backup options in the xHOSTING Control Panel (XCP).

The public profile does not define a particular destination type, pricing model, or guarantee of self-service restoration.

Is a specific backup method or destination guaranteed?

No. The public web hosting profile records a backup capability but does not promise a particular protocol, external provider, or destination type.

Always rely on the options currently shown in XCP.

Can backups be restored independently?

Self-service restoration depends on the current backup configuration; the public profile does not provide a general guarantee.

Keep your own regularly verified backup of important data, and test the restoration process before an emergency.

Why does xHOSTING emphasize security in package design?

xHOSTING operates as a controlled-access, community-based system where multiple Members share the same infrastructure. Therefore, security is not only an individual matter but also a community interest.

The goal of package design is to ensure that every Member can work in a stable, predictable, and secure environment, without any single user’s activity endangering the entire system.

How does xHOSTING protect the community infrastructure against abuse?

The documented community protections include:

• resource limits (CPU, memory, processes);
• restricted SSH access;
• community moderation and policy-based enforcement.

The public profile does not name a specific user-isolation technology or monitoring implementation.

How does the security model of community-based hosting differ from commercial hosting?

With community-based hosting, the focus is on shared responsibility and sustainability, rather than serving individual overuse.

While a commercial provider often operates with overselling and an SLA, xHOSTING’s model is built more on:

• conservative resource allocation,
• predictable load,
• and compliance with community rules

which enables more stable and secure operation in the long run.

Why is it important for every Member to respect resource limits?

Respecting resource limits ensures that every Member receives equal and predictable access to the community infrastructure.

If a Member exceeds or ignores these limits, it can:

• slow down or disrupt other Members’ services;
• create stability and security risks;
• trigger community measures (WARN, restriction).

The foundation of xHOSTING’s operation is conscious, responsible resource usage.

Why aren’t all features available by default?

xHOSTING packages are intentionally designed with conservative default settings. The goal is to preserve the stability, security, and long-term sustainability of the community infrastructure.

Some features—such as remote database access or special runtime capabilities—may involve increased risk or resource load, therefore they are not automatically available to every Member.

What does it mean when a feature is “available upon request”?

Features “available upon request” are options that are not part of the base package, but may be enabled in justified cases, based on individual assessment.

This means the Member may justify the need for the feature (e.g., for development, testing, or compatibility reasons), and xHOSTING operations will assess whether enabling it would not endanger the community operation. In this case, the Technical Operator will monitor the resource usage of the enabled feature with special attention and its impact on the community infrastructure.

What criteria are used to assess individual requests?

When assessing individual requests, the following key factors are considered:

• the technical and security risk of the requested feature;
• the expected level of resource usage;
• the impact on the community infrastructure;
• the Member’s prior community conduct and rule compliance;
• the justification and purpose of the request.

The purpose of assessment is not to obstruct, but to maintain responsible, community-friendly operation.

Can a request be rejected, and if so, why?

Yes, an individual request can be rejected if fulfilling it would:

• pose a security risk;
• cause disproportionate resource load;
• conflict with xHOSTING’s community principles;
• endanger other Members’ services;
• be insufficiently justified.

Rejection is not a sanction, but a technical decision aimed at protecting community operation.

Is Perl/CGI available?

Yes. Perl/CGI is an available feature of the unified web hosting profile.

Its use is subject to the same acceptable-use rules and community resource limits as other runtime options.

What should I consider when using Perl/CGI?

Perl/CGI is available, but scripts must be operated securely and efficiently like any other server-side code:

• keep code and dependencies up to date;
• do not store credentials in publicly accessible files;
• avoid unnecessary execution and excessive resource use;
• validate inputs and review file permissions.

Is an individual request required to use Perl/CGI?

No. Perl/CGI is part of the unified web hosting profile, so its profile-compliant use does not require an individual permission request.

Usage remains subject to the Acceptable Use Policy and documented resource limits.

In what environment does Perl/CGI run?

Perl/CGI runs according to the web hosting environment’s current server-side configuration.

The public profile does not claim a particular isolation or directory-access model. For security, rely only on files and resources belonging to your own hosting service.

Why is remote database access not available by default?

Remote database connections are unavailable by default and TCP port 3306 is closed.

This reduces the public network attack surface; the default model is database access from within the hosting environment.

What risks come with public database access?

Typical risks of public database access include:

• brute-force (password guessing) and automated bot attacks;
• exploitation of vulnerabilities (old clients, misconfiguration, protocol attacks);
• data leakage due to weak passwords or incorrect permissions;
• DoS / overload (many connections, high query volume, resource exhaustion);
• continuous reconnect due to a misconfigured client, generating load.

Since attackers commonly scan the internet en masse for database ports, public access by itself turns the service into a target.

When can remote database access be requested?

It can be requested only when the technical need can be explained in detail.

The request must be submitted through the Support system; access always requires individual review and separate approval.

How is remote database access securely restricted?

If approved, the exception can be enabled only for 1 specified source IP address.

This is not unlimited or public internet database access, and TCP port 3306 remains closed to other sources.

Why is the SSH environment restricted in the XBASIC package?

Limited SSH enables hosting-related command-line work without providing full system-level access.

This supports predictable use of community resources, but the public profile does not claim a particular isolation technology.

Can SSH be used for development or maintenance purposes?

Yes. The limited SSH environment can be used for hosting management, development, or maintenance tasks that are actually available there.

Check the availability of a specific tool or command in the current environment before relying on it.

Where can the limited SSH command set be checked?

The public web hosting profile does not maintain a guaranteed list of allowed or blocked commands.

Check the required command in the current SSH environment; access does not provide full system-level privileges.

What counts as excessive or unjustified resource usage?

Excessive or unjustified resource usage includes any activity that places a disproportionate load on xHOSTING’s community infrastructure and may negatively affect other Members’ services.

This includes, in particular:

• persistently high CPU or memory usage;
• continuously running unoptimized or faulty applications;
• unjustifiably heavy I/O or database load;
• automated scripts, crawlers, or background jobs running too frequently;
• loads not compatible with the package purpose (e.g., mining, stress testing).

Assessment is always made with the community operation and the package boundaries in mind.

How does the system detect abnormal load?

xHOSTING’s infrastructure monitors resource usage on multiple levels. The system uses automated monitoring and logging to detect patterns that deviate from normal, intended operation.

Monitoring may cover, among other things:

• CPU and memory usage spikes;
• long-running or stuck processes;
• unusual database or file operations;
• disproportionate network traffic.

The goal is not constant surveillance of Members, but early detection of situations that threaten community stability.

What happens if a Member continuously overloads resources?

If a Member’s resource usage causes sustained or repeated overload, xHOSTING may intervene to protect the community.

Possible measures may be gradual, for example:

• temporarily limiting or stopping affected processes;
• temporarily suspending a specific service;
• narrowing permissions;
• in serious or repeated cases, terminating membership.

The goal in every case is to restore community operation, not to punish.

Is there a warning before restrictions are applied?

Yes. xHOSTING aims to inform Members in advance about the issue whenever technically and practically possible.

In practice, this typically happens as:

• a warning (WARN);
• a brief explanation of the detected issue;
• recommendations to reduce load or fix the application.

Immediate intervention without prior warning occurs only if the load directly threatens the system or other Members’ operation.

What does the 10-scheduled-task limit mean?

One xHOSTING account can contain up to 10 separate scheduled (cron) jobs. They can run at defined intervals for maintenance or application tasks.

The purpose of the limit is not to reduce functionality, but to ensure the number of scheduled processes remains proportional to community resources.

Can cron jobs be used for long-running operations?

Scheduled tasks are primarily meant for short-running, well-defined operations. Running long-running or continuously load-generating tasks from cron (such as large data processing or infinite loops) is not recommended.

If a task would legitimately run longer, it is advisable to optimize it, split it into smaller parts, or find a solution through individual coordination. Such loads can endanger the stability of the community infrastructure.

Why is limiting scheduled tasks important in a community environment?

In community-based hosting, scheduled tasks are a sensitive area because they can load the system at the same time and at unpredictable moments.

The purpose of the limit is to:

• avoid sudden load spikes;
• ensure fair sharing of community resources;
• prevent one Member’s automated processes from degrading others’ services;
• preserve the system’s long-term stability.

Using scheduled tasks consciously is in every Member’s shared interest for reliable operation.

Why doesn’t xHOSTING provide an SLA?

xHOSTING is not a classic, business-based hosting service, but a community system built on voluntary contributions. Accordingly, it does not offer a contractual service level (SLA), because an SLA would legally and technically imply business operation, guaranteed resources, and continuous availability.

The community model aims for sustainable, fair, and transparent operation—not the fulfillment of commercial commitments.

What does it mean in practice that there is no guaranteed uptime?

The lack of guaranteed uptime means that xHOSTING does not promise a specific availability percentage. Services generally run stably, but temporary outages may occur.

Operations aim for continuous service, but there is no legal or financial obligation to meet a defined uptime level.

Which contractual commitments are not included with the community service?

The free community service does not include contractual commitments typical of classic business hosting:

• no SLA or guaranteed uptime;
• no outage-related penalty or service credit;
• no paid customer-support priority.

This question clarifies the scope of contractual commitments; the earlier overview covers the broader differences of the community operating model.

In which cases can service outages occur?

Service outages may occur, among other things, in the following cases:

• during planned maintenance or updates;
• due to unexpected hardware or software failures;
• when preventing or handling a security incident;
• due to issues in external infrastructure (e.g., network connection, power supply);
• as a consequence of abnormal or excessive load.

Handling such situations always serves to protect the community as a whole and ensure long-term operation.

What is the xHOSTING Control Panel (XCP), and what is it used for?

The xHOSTING Control Panel (XCP) is xHOSTING’s unified control interface through which Members can manage settings related to their hosting and services.

Using XCP, you can manage, among others:

• domains and subdomains;
• email accounts and forwards;
• databases;
• files and FTP/SFTP access;
• PHP version selection and viewing fixed PHP limits;
• backups;
• certificates and domain security features.

The control panel’s purpose is to provide independent, transparent, and secure administration without installing separate client software.

What system is the xHOSTING Control Panel (XCP) built on?

The technical foundation of the xHOSTING Control Panel (XCP) is provided by a modern, Linux-based hosting management system.

xHOSTING has built a multi-year professional relationship with the control panel’s developers, is the official language localizer of the system, and therefore has access to the full functionality of the commercial edition, receiving advance notice of all updates and changes before release. XCP uses a customized interface and permission model aligned with xHOSTING’s operation and rule set, providing a consistent xHOSTING experience for users.

Why was the xHOSTING Control Panel (XCP) chosen as the control panel?

The selection of the xHOSTING Control Panel (XCP) is the result of several professional and community considerations:

• a modern, actively developed system;
• transparent permission management and resource limiting;
• good integration with PHP, FTP, SSH, email, and backup functions;
• no per-user licensing required;
• suitable for a community-based hosting model.

The system enables xHOSTING to operate a secure, sustainable, and flexible infrastructure without business-type constraints.

How does XCP differ from a classic cPanel or Plesk system?

XCP differs from classic commercial control panels (such as cPanel or Plesk) in several key ways:

• very user-friendly;
• it is not aligned with a business hosting model;
• it does not include features tied to SLAs or customer support priority;
• it applies stricter, community-based resource and permission management;
• security and sustainability are primary considerations.

While cPanel and Plesk are designed for mass commercial customer hosting, XCP is tuned specifically to the needs of a controlled-access community.

Can all functions be used from a browser without installing anything?

Yes. The xHOSTING Control Panel (XCP) is fully usable from a web browser, without installing any additional software or client.

Most administrative tasks—such as file management, database administration, email settings, or backup management—are available directly through the browser.

For some advanced functions (e.g., an FTP client, an SSH connection, or an external email program), external tools can be used optionally, but they are not required to use XCP.

How do you log in to the xHOSTING Control Panel (XCP)?

Logging in to the xHOSTING Control Panel (XCP) is done by entering a unique username and password on a web interface available over HTTPS.

The login credentials are created when membership is activated and are linked exclusively to the Member’s own account. The connection is always encrypted, so authentication data is not transmitted in plain form.

Can two-factor authentication (2FA) be used in XCP?

Yes. The xHOSTING Control Panel supports two-factor authentication (2FA), which provides an additional layer of protection for user accounts.

After enabling 2FA, logging in requires not only the password but also a time-based one-time code generated by an authenticator app (e.g., on a mobile phone).

Using two-factor authentication is strongly recommended for every Member.

What can a Member do if they forget their password?

In case of a forgotten password, the Member can use the password reset function available on the login page.

The system then sends a verification message to the contact email address associated with the account, through which a new password can be set.

For security reasons, the old password cannot be recovered—only a new password can be created.

Does the system log logins and failed attempts?

Yes. The xHOSTING Control Panel logs successful and failed login attempts for security purposes.

Logging helps detect suspicious activity, protect accounts, and investigate potential abuse.

In case of repeated failed login attempts, the system may apply automatic protective measures (e.g., temporary restriction).

How can you add a new domain in XCP?

Adding a new domain in the xHOSTING Control Panel (XCP) is done through the menu section dedicated to domain management.

The Member can enter the domain name, select its type (primary domain, alias, or subdomain), then configure the related web, email, and DNS parameters. After activation, the system automatically creates the required directory structure and default settings.

What is the difference between a primary domain, an alias domain, and a subdomain?

Primary domain: an independent domain with its own web content and settings (e.g., mydomain.hu).

Alias domain: an additional domain pointing to an existing primary domain, serving the same content (e.g., mydomain.com → mydomain.hu).

Subdomain: a logical unit under the primary domain with a separate address (e.g., blog.mydomain.hu), which can be linked to a separate directory and even a separate application.

How many domains and subdomains can be used in the XBASIC package?

The unified profile allows up to 5 domains and 10 subdomains in total across the complete profile.

Domain allocation is flexible, but the defined limits cannot be exceeded in order to balance community resource usage.

Can a primary domain be deleted from XCP?

Yes. The Member is allowed to delete their own primary domains through the xHOSTING Control Panel.

Before deletion, the system shows a warning because the action is irreversible and the services associated with the domain will stop.

What happens to the domain’s data when it is deleted?

When a domain is deleted, the related web files, database links, email accounts, and other settings become inactive and may then be permanently removed after a technical delay.

It is the Member’s responsibility to back up data before deletion. xHOSTING does not assume liability for data loss resulting from deletion.

Which DNS records can be managed in XCP?

In the xHOSTING Control Panel (XCP), the most commonly used DNS record types can be fully managed.

These include in particular A, AAAA, CNAME, MX, TXT, SRV, and CAA records. Using these, you can configure web hosting, email routing, and various security and authentication mechanisms (e.g., SPF, DKIM, DMARC).

Can you use your own DNS servers per domain?

Yes. A Member may decide not to use xHOSTING-provided DNS management for a given domain, and instead configure their own or external DNS servers.

In that case, the domain’s nameservers (NS records) must be changed at the registrar. It is important to note that with this configuration, the Member is responsible for DNS operation and any related issues.

When is manual DNS editing not recommended?

Manual DNS record changes are not recommended if the Member is not confident about the effects of the settings or lacks experience managing DNS configurations.

Incorrect entries may cause the website, email service, or other related functions to become temporarily or permanently unavailable. Extra care is required when modifying MX and TXT records.

How long does it take for DNS changes to take effect?

DNS changes do not take effect instantly; they depend on so-called DNS propagation.

This can typically take anywhere from a few minutes up to 24–48 hours, depending on the record’s TTL value and the caching practices of internet service providers.

What are xHOSTING’s own nameservers?

xHOSTING provides its own centrally operated nameservers for the community hosting service.

The current, official list of xHOSTING nameservers is always available in the xHOSTING Control Panel (XCP) and in the documentation. This is because the nameserver endpoints may change as the infrastructure evolves or undergoes technical restructuring, and the information published there is always authoritative.

Current nameservers:

• ns1.xhostingcore.xyz
• ns2.xhostingcore.xyz

After making changes, DNS delegation updates typically take from a few minutes up to 24–48 hours due to how the global DNS system works.

How can I set my domain’s nameservers to xHOSTING at another provider?

If your domain is registered with an external registrar or provider, you must change the nameservers there.

The steps are generally:

• log in to your domain registrar’s management interface;
• find the domain’s nameserver settings;
• replace the current nameservers with the nameservers provided by xHOSTING;
• save the changes.

After the change, DNS delegation updates typically take from a few minutes up to 24–48 hours due to how the global DNS system works.

If I use my own or another provider’s nameservers, how do I point my domain to xHOSTING hosting?

In this case, the domain’s DNS zone is not managed by xHOSTING, but by the external nameserver provider.

You must then configure the following DNS records correctly:

• A record – point the domain(s) to the xHOSTING server’s IPv4 address;
• AAAA record – if IPv6 is used, provide the IPv6 address;
• MX record – if you use xHOSTING email, set the records for the email servers;
• TXT records – as needed (e.g., SPF, DKIM, DMARC).

XCP shows, for each domain, the IP addresses and recommended record values required for proper web and email operation.

Important: if you use external DNS, the accuracy of the DNS configuration is entirely the domain owner’s responsibility. If records are incorrect or missing, the website or email service will not work properly.

What file management options does XCP provide?

The xHOSTING Control Panel (XCP) provides multiple file management options for Members.

Files can be managed via traditional FTP / SFTP connections, as well as via the browser-based file manager built into XCP. With these methods, you can upload, download, delete, rename files, change permissions, and manage directory structures.

Can the built-in file manager be used without FTP?

Yes. XCP’s built-in file manager can be used entirely without FTP or an external client.

The file manager is accessible from a web browser and provides a practical solution for basic administration tasks (quick edits, editing configuration files, small uploads).

With what permissions can files be accessed?

The current account and directory permissions determine the actual scope of file access; when managing files, rely only on resources belonging to your own hosting account.

The public profile does not define a specific isolation technology or detailed filesystem permissions model.

Can deleted files be restored from XCP?

The public profile does not guarantee a recycle bin, versioning, or automatic restoration. Check the currently available options in XCP.

Restoration is possible only from a usable earlier backup, so keep your own verified copy and regularly test that it can be restored.

How can a new FTP user be created?

A new FTP user can be created in the xHOSTING Control Panel (XCP) independently, without administrator intervention.

The general steps are:

• log in to XCP
• open the FTP users menu
• add a new FTP user
• set the username and password
• select the home directory

The created FTP user can be used immediately with the specified credentials.

Can an FTP user be restricted to a specific directory?

Yes. XCP allows an FTP user to be limited to access only a specific directory.

Benefits of directory restriction:

• the user cannot see the full hosting directory structure
• it reduces the risk of accidental or intentional data damage
• it is ideal for developers, subcontractors, or partial-task access

The restriction can be set during user creation or later.

Does the FTP-user limit apply per domain or to the complete profile?

The limit applies to the complete web hosting profile: up to 5 FTP users can be created in total, not that many per domain.

Deleting an FTP user that is no longer needed frees one slot within the documented limit.

Can FTPS or SFTP be used in XCP?

Yes. In addition to FTP, xHOSTING also supports encrypted connections.

Available options:

• FTPS – FTP over an encrypted TLS connection
• SFTP – secure file transfer over SSH

Using SFTP requires SSH access to be enabled, while FTPS can be used without SSH access.

Using encrypted connections is strongly recommended, especially when connecting from a public or untrusted network.

How can the PHP version be selected per domain?

The xHOSTING Control Panel (XCP) allows selecting the PHP version separately for each domain.

The setup process:

• log in to XCP
• open the domain management section
• select the desired domain
• set the PHP version for that domain

This makes it possible to run multiple websites under one hosting account with different PHP versions, depending on each application’s requirements.

What does XCP show about the fixed PHP limits?

XCP may display the centrally fixed PHP resource limits:

• memory_limit: 256M
• max_execution_time: 180 seconds
• post_max_size: 128M
• upload_max_filesize: 128M

These values cannot be changed in XCP or through a custom php.ini file. Selecting a PHP version per domain is a separate feature.

What do the fixed PHP resource limits mean?

The central profile fixes four values: memory_limit 256M, max_execution_time 180 seconds, post_max_size 128M, and upload_max_filesize 128M.

• memory_limit – the maximum memory a single PHP process can use
• max_execution_time – the maximum runtime of one PHP script
• post_max_size – the maximum size of one POST request
• upload_max_filesize – the maximum size of a single uploaded file

These limits help to:

• prevent excessive resource usage
• keep the community environment stable
• reduce the impact of faulty or malicious scripts

The limits cannot be changed through a custom php.ini file or in XCP.

What is open_basedir, and why is it important?

open_basedir is a PHP security restriction that defines which directories a PHP script is allowed to access.

The public hosting profile does not state whether this setting is active or define its value or scope. Check the current PHP environment before installing an application; open_basedir alone does not prove complete isolation.

What does the disable_functions list mean?

The disable_functions list contains PHP functions that are disabled for security reasons.

The public profile does not define a permanent function list. Check the actual setting in the current PHP environment when evaluating application compatibility.

How can a new database be created in XCP?

Creating a new database in the xHOSTING Control Panel (XCP) can be done in a few steps.

The creation process:

• log in to XCP
• open the database management section
• select the option to create a new database
• enter the database name and the associated user
• set a password or generate one automatically

The created database can be used immediately for web applications or custom development.

Which database types are supported?

The public web hosting profile defines the number of databases but does not name a specific database engine or engine version.

Check the currently supported type and version in XCP, then compare them with the requirements of the application you intend to use.

Does the database limit apply per domain or to the complete profile?

The complete web hosting profile allows 5 databases in total; the limit is not repeated for every domain.

Each created database uses one slot from this shared limit, and deleting it frees that slot.

Is a web-based database manager available (e.g., phpMyAdmin)?

Yes, XCP provides a web-based database management interface that is accessible from a browser.

The web database manager allows:

• creating and modifying tables
• viewing and editing data
• running SQL queries
• exporting and importing databases

Access is restricted by the permissions assigned to the given database, so only your own databases can be managed.

How can a new email account be created in XCP?

You can create a new email account in the xHOSTING Control Panel (XCP) via the email management interface.

General steps:

• log in to XCP
• open the Email / Mailboxes menu
• choose the option to create a New mailbox
• enter the address (e.g., info@domain.tld) and the password
• save the settings

The profile allows 10 email accounts in total. After creation, the account can be used via webmail and an email client.

When should you create a separate email address, and when do you need a real mailbox?

In short: if you only want emails to be forwarded to another mailbox, an email address (alias or forwarding) is sufficient. If you need a separate login with its own storage space, you must create a real email account (mailbox).

Practical examples:

• Forwarding (alias): info@domain.hu → emails are automatically forwarded to your Gmail or another mailbox.
• Real mailbox: separate login (IMAP/POP3), dedicated storage space, password protection, usable across multiple devices.

This helps you decide whether you need an actual mailbox or if simple forwarding is enough.

What delivery and spam risks come with using catch-all?

The catch-all feature available in the unified profile can direct every message sent to a non-existent address on the domain to the selected mailbox.

Catch-all means:

• emails sent to non-existing addresses under the domain are still delivered
• messages arrive in a designated mailbox (e.g., catchall@domain.tld or admin@domain.tld)

Note:

• catch-all often attracts more spam, so it should only be enabled if truly necessary
• if you receive too much unsolicited mail, it is usually better to create specific addresses or use filtering

How does email forwarding work in XCP?

Yes. The unified profile allows up to 20 email forwarders.

What forwarding is useful for:

• messages are automatically redirected to another address (e.g., a Gmail address)
• useful if you do not want a separate mailbox, only to redirect incoming mail

Recommendation:

• if you expect a lot of mail, it is often better to use a mailbox and handle flows with rules
• avoid circular forwarding (A → B → A), because it can cause delivery errors or an infinite loop

Where can email passwords and quotas be managed?

Email passwords and (if available) quotas can be managed in XCP under the mailbox’s details.

Typically you will find it here:

• Email / Mailboxes list
• select mailbox → Edit
• Change password and quota settings

Security minimum:

• use a long, unique password (recommended: generate with a password manager)
• if you notice suspicious activity, change the password immediately and review client settings

How does a Let’s Encrypt certificate work in XCP?

In XCP, Let’s Encrypt allows you to enable a free, automatically issued SSL/TLS certificate for your domains.

General flow:

• select the domain in the certificate/SSL section
• enable Let’s Encrypt issuance
• the system performs a technical verification (domain validation), then issues the certificate

Common prerequisites:

• the domain’s DNS already points to the xHOSTING server
• web service is reachable (validation is not blocked by a firewall or incorrect redirects)

Do SSL certificates renew automatically?

Yes, renewal of Let’s Encrypt certificates is basically automatic, as long as the domain can still be successfully validated at the time of renewal.

Typical reasons why renewal can fail:

• the domain no longer points to xHOSTING
• DNS issues or incorrect records
• HTTP/HTTPS access required for validation is blocked
• incorrect or overly aggressive redirect rules

If renewal is problematic, the process can typically be restarted / re-requested in XCP.

What is HSTS, and when should it be enabled?

HSTS (HTTP Strict Transport Security) is a browser-side security rule that forces the browser to access the domain only over HTTPS.

Benefits:

• reduces the chance of “downgrade” and man-in-the-middle attacks
• the browser automatically switches to HTTPS

When it is worth enabling:

• once HTTPS is confirmed to work on every page
• if you do not use external resources that are available only over HTTP

Warning:

• with HSTS, a broken HTTPS setup can “lock you out” due to browser caching
• it is recommended to test first with a short max-age value, then increase it later

What does the “add includeSubDomains” directive mean?

includeSubDomains is a security directive that extends HTTPS-only behavior not just to the main domain, but also to all existing subdomains.

Practical meaning:

• every subdomain becomes accessible only via HTTPS
• browsers automatically reject unencrypted (HTTP) connections
• reduces the risk of man-in-the-middle attacks

Important note:

• this is a one-time action that applies to the subdomains that exist at the time
• if you create new subdomains later, the setting must be updated manually

What does the “add preload” directive mean?

The preload directive indicates that the domain may be submitted to the HSTS preload list used by browsers.

In practice this means:

• browsers allow only HTTPS even on the very first connection
• there is no HTTP access, not even for redirect-based upgrades
• it provides extra protection during the first connection

Important constraints:

• using preload also requires includeSubDomains
• it is a long-term commitment to HTTPS
• removal from the preload list takes time and is not immediate

Therefore, using preload is recommended only if you are sure that all subdomains will remain on HTTPS long-term.

What does it mean to apply security settings to all subdomains?

This means that the selected security rules (for example, HTTPS enforcement, HSTS, includeSubDomains) apply not only to the main domain, but also to all existing subdomains.

Benefits:

• a consistent security level across all subdomains
• fewer configuration mistakes
• better protection against accidentally exposed services

Important to know:

• this setting does not automatically inherit to subdomains created in the future
• when adding a new subdomain, security settings must be refreshed manually
• if HTTPS support is broken or incomplete, a subdomain may become unreachable

Recommendation:

• apply it globally only if every subdomain is properly configured
• after creating a new subdomain, always verify the security settings

Can I upload my own certificate?

Yes. If you have your own SSL/TLS certificate (for example, EV/OV or one issued by an external CA), you can upload it in XCP.

You typically need:

• the certificate (CRT/PEM)
• the private key (KEY)
• optionally, an intermediate chain (CA bundle)

Recommendation:

• if you do not specifically need an external CA, Let’s Encrypt is simpler and renews automatically
• use your own certificate if you need organizational validation (OV/EV) or special compliance requirements

How does backup management work in XCP?

The unified web hosting profile includes a backup capability, and the currently available management options are shown in the xHOSTING Control Panel (XCP).

The public profile does not promise a specific backup frequency, retention period, destination type, or guaranteed restoration.

How can the current backup settings be checked in XCP?

After signing in, use the XCP interface for backup features to verify which settings and destinations are actually available at that time.

The public profile does not list guaranteed protocols, external providers, or destination types, so their availability must not be assumed.

Is a backup schedule or frequency guaranteed?

No. The public profile does not promise automatic, daily, weekly, or any other fixed backup frequency.

Check the current options in XCP, and regularly verify both the existence and restorability of backups with a test.

Who is responsible for regular data backups?

Due to the community operating model, responsibility for regular data backups lies primarily with the Member.

In practice, this means:

• the Member is responsible for defining an independent backup strategy
• the Member is responsible for checking backups and testing restoration
• xHOSTING does not provide a guaranteed, business-style backup obligation

Recommendation:

• for critical data, always keep multiple independent backup copies
• periodically verify that backups exist and are usable

What kind of spam filtering does xHOSTING use?

xHOSTING applies multi-layer, server-side spam filtering to protect email traffic.

The goal of the filtering is to block clearly unwanted messages before delivery, while ensuring that legitimate emails are delivered reliably. The system takes into account factors such as sender reputation, technical authentication checks, and content characteristics.

Does xHOSTING use SPF, DKIM, and DMARC protection?

xHOSTING’s server-side spam filtering uses a multi-layer protection model.

The system is based on statistical analysis, adaptive (machine-learning-based) scoring, and authentication checks (SPF, DKIM, DMARC). This makes it possible to filter out a large portion of unsolicited emails before delivery.

What does “machine-learning-based” spam filtering mean?

Machine-learning-based spam filtering means that the system analyzes email characteristics using statistical methods.

The filter evaluates factors such as message content, header data, sending patterns, and previous observations. Based on these signals, it continuously refines its scoring, allowing it to distinguish legitimate messages from spam more effectively over time.

Does the spam filter learn over time?

Yes. The spam filter operates in an adaptive manner.

The system continuously improves detection based on patterns found in incoming messages. This means that common spam types are identified with increasing accuracy over time, while the likelihood of false positives is reduced.

What happens to emails classified as spam?

Emails classified as spam are typically not deleted immediately.

The system marks such messages as spam or handles them in a separated manner, allowing them to be reviewed if necessary. The exact behavior also depends on the email account settings and client-side filtering rules.

Can a legitimate email be marked as spam?

Yes, in rare cases a so-called “false positive” may occur, where a legitimate email is classified as spam.

This typically happens when the sender’s domain is misconfigured, authentication records are missing, or unusual content patterns are detected. In such cases, it is recommended to review the sender’s technical configuration or whitelist the sender in the email client.

Can I do anything to reduce the amount of spam?

Yes. The amount of spam can be significantly reduced with conscious configuration and usage.

Recommended steps:

• use only necessary email addresses and avoid publishing them publicly;
• use separate addresses for registrations;
• ensure that your domain’s SPF, DKIM, and DMARC records are configured correctly;
• use the filtering and rule features provided by your email client.

The combination of server-side protection and user awareness provides the best results.

Can a completely spam-free email service be guaranteed?

No. A completely spam-free email service does not exist.

The goal of xHOSTING is to filter out the vast majority of unsolicited messages while reliably delivering legitimate emails. Spam protection is a continuous balance between strict filtering and safe message delivery.

Is xhosting.hu affiliated with similarly named providers?

No.

The domain xhosting.hu is not affiliated with any other similarly named foreign or domestic hosting provider (e.g., x10hosting).

What are the requirements for registering a .hu domain?

.hu domain registration is subject to eligibility requirements.

The domain holder must be either a citizen or a legal entity of one of the following countries: Andorra, Albania, Armenia, Austria, Azerbaijan, Belgium, Bosnia and Herzegovina, Bulgaria, Czech Republic, Cyprus, Croatia, Denmark, Estonia, Finland, France, Germany, Georgia, Greece, Hungary, Ireland, Iceland, Italy, Liechtenstein, Lithuania, Luxembourg, Latvia, Macedonia, Malta, Monaco, Moldavia, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, Serbia, San Marino, Slovenia, Slovak Republic, Spain, Sweden, Switzerland, Turkey, Ukraine.

Alternatively, the applicant may also qualify if they carry out or start an economic or other activity that justifies the use of a .hu domain name.

The Registry may request supporting documents and reserves the right to reject the registration if the submitted documents are not satisfactory or for other reasons.

The user is solely responsible for meeting these requirements. If the registration cannot be completed because the requirements are not met or the Registry rejects the application, no refund will be issued.

What are the requirements for registering a .eu domain?

.eu domain registration is subject to eligibility requirements.

The registrant must have an address in one of the European Union member states, Iceland, Liechtenstein, or Norway, or hold citizenship in one of those countries.

The Registry may request proof of citizenship, especially if the registrant resides outside the European Economic Area.

The user is solely responsible for meeting these requirements. If the registration cannot be completed because the requirements are not met or the Registry rejects the application, no refund will be issued.

What are the requirements for registering a .fr domain?

.fr domain registration is subject to eligibility requirements.

The registrant and the administrative contact must have an address in one of the European Union member states or in one of the following countries: Iceland, Liechtenstein, Norway, or Switzerland.

Eligible countries and territories include for example: Austria, Aland Islands, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, French Guyana, Germany, Gibraltar, Greece, Guadeloupe, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Martinique, Mayotte, Netherlands, New Caledonia, Norway, Poland, Portugal, Reunion Island, Romania, Saint Pierre and Miquelon, Slovak Republic, Slovenia, Spain, Sweden, Switzerland, French Southern and Antarctic Lands, Wallis and Futuna.

.fr domains are also available through our trustee service.

The user is solely responsible for meeting these requirements. If the registration cannot be completed because the requirements are not met or the Registry rejects the application, no refund will be issued.

What are the requirements for registering a .it domain?

.it domain registration is subject to eligibility requirements.

The registrant must be either an individual residing in the European Union or an organization registered in the European Union with a valid VAT number.

.it domains are also available through our trustee service.

The user is solely responsible for meeting these requirements. If the registration cannot be completed because the requirements are not met or the Registry rejects the application, no refund will be issued.

What are the requirements for registering a .sk domain?

.sk domain registration is subject to eligibility requirements.

The registrant may be any natural or legal person that has a postal address in any European Union member state, in a state within the European Economic Area, or in a member state of the European Free Trade Association.

.sk domains are also available through our trustee service.

The user is solely responsible for meeting these requirements. If the registration cannot be completed because the requirements are not met or the Registry rejects the application, no refund will be issued.

Is free game server hosting available on xHOSTING?

Yes. xHOSTING provides free game server hosting on a controlled-access, community basis.

It does not work as a purchasable hosting package. Access depends on finite community capacity, with a focus on stable, transparent operation and support for smaller gaming communities.

Which game server types are supported?

According to the current public resource limits, xHOSTING supports MTA, GTA5 (M), and ARK game servers.

Detailed resource limits — such as RAM, storage, CPU, maximum players, ports, backups, and databases — are listed in the supported game server types table on the landing page.

Is free GTA5 (M) server hosting available?

Yes, xHOSTING also supports GTA5 (M) game servers through approved community access. Detailed resource limits are available here.

The public website intentionally uses the GTA5 (M) naming format. Available capacity is finite, so actual availability always depends on current community resources.

Is free MTA server hosting available?

Yes, xHOSTING provides MTA game servers with community-based, approved access. Detailed resource limits are available here.

MTA servers are suitable for smaller communities, friendly gameplay, development, and testing. The goal of the limits is not mass hosting, but stable operation.

Is there a free ARK: Survival Evolved server?

Yes, xHOSTING provides ARK: Survival Evolved game servers with a community-based, controlled-access model. Detailed resource limits are available here.

ARK servers are available with limited capacity, so they are mainly intended for smaller communities, casual gameplay and testing.

Who needs to submit an access request?

xHOSTING is built on finite resources and community trust. Users registering with a valid invitation receive ordering rights immediately, while users registering without an invitation do not receive ordering rights automatically.

For users registering without an invitation, the access request helps prevent abuse, over-allocation, and overload. It is not a barrier for its own sake, but a tool for keeping the system stable and sustainable. Users registering with a valid invitation do not need a separate access request.

Is xHOSTING a commercial hosting provider?

No. xHOSTING is not a traditional commercial hosting provider.

Community web hosting and game server hosting do not operate as subscription packages. The focus is on learning, testing, development, hobby projects, and supporting smaller communities.

What does GTA V RP mean within the GTA5 (M) resource model?

On the public website, GTA V RP means roleplay-style GTA V multiplayer community servers covered by the GTA5 (M) resource model. The exact limits are listed here.

It is not a separate capacity category: availability depends on current GTA5 (M) community capacity and approved access.

Is there DDoS protection on xHOSTING?

Yes, xHOSTING uses network-level DDoS filtering and server-side firewall protection.

This does not mean unlimited or guaranteed attack protection, but it helps reduce the attack surface and improves the stable operation of web hosting and game servers.

How does xHOSTING use registration data?

xHOSTING does not misuse information provided during registration, does not sell it, and does not process it for broader purposes than necessary.

The primary purposes of the data are account administration, communication, access request review, and fulfilling billing or administrative obligations if fee-based services are used in the future.

Users may request deletion of their data at any time via email or a support ticket in the client area. Where legal retention obligations apply, xHOSTING keeps only the data that must be retained for the required period.