I am reporting a severe technical failure by x10Hosting that effectively holds my domain hostage.
Domain: tusecreto.x10.mx
Server IP: 198.91.80.155
THE ISSUE:
Their system failed to purge the VirtualHost and DNS configuration after account termination. I have verified this is a server-side "Ghost Record" because the domain remains locked even when I try to register it on a completely different account.
The error "Domain already exists on 198.91.80.155" is hard-coded in their backend.
ESCALATION TAKEN:
- Formal complaint filed with NIC México (Legal Dept) for .MX mismanagement.
- ICANN Case #01557634 opened.
- Upstream provider (INAP/SingleHop) notified of this technical negligence.
I am posting here to warn the community and demand that an x10Hosting System Admin manually clears the orphaned configuration on server 198.91.80.155. Support has been non-responsive for days.
Any advice from the community on how to force a cleanup of orphaned records when the host is silent?
Domain: tusecreto.x10.mx
Server IP: 198.91.80.155
THE ISSUE:
Their system failed to purge the VirtualHost and DNS configuration after account termination. I have verified this is a server-side "Ghost Record" because the domain remains locked even when I try to register it on a completely different account.
The error "Domain already exists on 198.91.80.155" is hard-coded in their backend.
ESCALATION TAKEN:
- Formal complaint filed with NIC México (Legal Dept) for .MX mismanagement.
- ICANN Case #01557634 opened.
- Upstream provider (INAP/SingleHop) notified of this technical negligence.
I am posting here to warn the community and demand that an x10Hosting System Admin manually clears the orphaned configuration on server 198.91.80.155. Support has been non-responsive for days.
Any advice from the community on how to force a cleanup of orphaned records when the host is silent?
Did you reach out to x10Hosting before coming here and writing this post, filing a formal complaint with NIC, ICANN, and INAP/SingleHop?
If I had to guess - your service was canceled/terminated for something and leaving the record active prevents you from simply signing up again and doing the same thing. I've known the owner of x10 for a couple of decades now and they run a tight ship. Usually terminations are for phishing, nulled software, spamvertisement, etc.
Beyond that - unless you own `x10.mx`, which I suspect you do not, you don't have a leg to stand on.
What happened to cause the account to be terminated?
If I had to guess - your service was canceled/terminated for something and leaving the record active prevents you from simply signing up again and doing the same thing. I've known the owner of x10 for a couple of decades now and they run a tight ship. Usually terminations are for phishing, nulled software, spamvertisement, etc.
Beyond that - unless you own `x10.mx`, which I suspect you do not, you don't have a leg to stand on.
What happened to cause the account to be terminated?
I am reporting a severe technical failure by x10Hosting that effectively holds my domain hostage.
Domain: tusecreto.x10.mx
Server IP: 198.91.80.155
What domain are you talking about? Or did you mean sub-domain?
Unless you own x10.mx, they are not holding your domain. It is theirs to keep even the sub-domain since they are the owner of the domain.
Your complaint will go nowhere.
THE ISSUE:
Their system failed to purge the VirtualHost and DNS configuration after account termination. I have verified this is a server-side "Ghost Record" because the domain remains locked even when I try to register it on a completely different account.
The error "Domain already exists on 198.91.80.155" is hard-coded in their backend.
I believe you are referring to the subdomain, as the top-level domain (TLD) x10.mx was registered in 2009 by x10.
It's important to note that you do not have any rights to the subdomain; it is a free service, and they retain full control over their service, subdomains, and the root domain itself.
I have verified this is a server-side "Ghost Record" because the domain remains locked even when I try to register it on a completely different account.
The error "Domain already exists on 198.91.80.155" is hard-coded in their backend.
Are you saying that you tried to register a new free account with them, but cannot use the same subdomain because it already exists? The best course of action would be to contact them directly and request the reinstatement of your account. According to their Terms of Service (TOS), "x10Hosting reserves the right to cancel any service provided at any time."
Moreover, they limit users to one active account only at any given time, and signing up for multiple accounts will result in a suspension of service.
Am I missing anything here?
To everyone focusing on the "Free Subdomain" aspect: You are missing the technical point.
This is not a complaint about "rights"; it is a report of a CRITICAL SYSTEM BUG (Ghost Record) on server 198.91.80.155.
Technical Reality:
1. When an account is terminated, the system MUST purge VirtualHost and DNS entries.
2. x10Hosting’s automated scripts FAILED to do this.
3. This is "Server Pollution." Leaving "Zombie Records" on a production server is objectively poor systems administration.
To Mike: I am not a "disgruntled user" trying to bypass a ban. I am a user documenting a backend failure where stale data is blocking system resources. Whether it's free or paid, a "Hard-Locked" record is a bug that requires a manual purge.
To those saying "it will go nowhere":
NIC México has already opened two official legal investigation tickets: #MA500319083 and #ML100319082. This is no longer just a forum post; it’s a documented case of .MX resource mismanagement.
I am simply demanding that a Senior Admin takes 30 seconds to run a manual deletion of the orphaned config files on 198.91.80.155. Defending a technical glitch just because the service is free is not a professional argument.
This is not a complaint about "rights"; it is a report of a CRITICAL SYSTEM BUG (Ghost Record) on server 198.91.80.155.
Technical Reality:
1. When an account is terminated, the system MUST purge VirtualHost and DNS entries.
2. x10Hosting’s automated scripts FAILED to do this.
3. This is "Server Pollution." Leaving "Zombie Records" on a production server is objectively poor systems administration.
To Mike: I am not a "disgruntled user" trying to bypass a ban. I am a user documenting a backend failure where stale data is blocking system resources. Whether it's free or paid, a "Hard-Locked" record is a bug that requires a manual purge.
To those saying "it will go nowhere":
NIC México has already opened two official legal investigation tickets: #MA500319083 and #ML100319082. This is no longer just a forum post; it’s a documented case of .MX resource mismanagement.
I am simply demanding that a Senior Admin takes 30 seconds to run a manual deletion of the orphaned config files on 198.91.80.155. Defending a technical glitch just because the service is free is not a professional argument.
What right do you have to open a formal complaint about a resource that is not yours? You got a free service, now terminated. What becomes of the DNS record on a server that's not under your control is not yours to govern. If the company leaves that in place (likely to prevent reuse of abusers), that's their choice.
Strong doubts it's a bug, and more likely intentional.
Strong doubts it's a bug, and more likely intentional.
They also have on their TOS that users are allowed to have only one active account: https://x10hosting.com/tos
Maybe it is intentional and they have a policy to prune those virtual hosts after x amount of time
Maybe it is intentional and they have a policy to prune those virtual hosts after x amount of time
To Bear, dkatsaris, and the rest of the "pro-host" crowd here:
Let’s separate professional system administration from your personal opinions about "free services."
1. THE PRIVACY & DATA CLAIM: Under GDPR and International Data Privacy standards, when a user requests account termination and data deletion, the provider is OBLIGATED to purge all associated records. Keeping "Ghost Records" (VirtualHosts/DNS zones) active after account deletion is a "Data Residue" failure. This is not a "choice"—it’s technical negligence.
2. THE "INTENTIONAL" ARGUMENT IS FLAWED: If x10Hosting is intentionally leaving orphaned records to "prevent abuse," they are effectively polluting their own IP space (198.91.80.155) with dead configurations. This is an amateur way to manage a network. A professional system uses blacklists, not "Zombified Configurations" that block legitimate future system resources.
3. LEGAL ESCALATION: You ask what "right" I have?
I have the right to report the mismanagement of .MX resources. NIC México has officially accepted the case (Tickets #MA500319083, #ML100319082). They do not care if the service is free or paid; they care about the integrity of the .MX namespace. If a provider cannot properly de-allocate a .MX subdomain, they are failing their responsibilities as a service provider in that region.
4. THE TECHNICAL DEADLOCK: The domain is "Hard-Locked." This means their automation script is broken. Period. Defending a broken script just because it's a free service shows a lack of technical standards.
I am not asking for your permission to complain. I am documenting a failure that x10Hosting refuses to fix. I will continue to update this thread with the findings from NIC México and ICANN.
Silence from support is not a "policy"—it's an admission of technical incompetence.
Let’s separate professional system administration from your personal opinions about "free services."
1. THE PRIVACY & DATA CLAIM: Under GDPR and International Data Privacy standards, when a user requests account termination and data deletion, the provider is OBLIGATED to purge all associated records. Keeping "Ghost Records" (VirtualHosts/DNS zones) active after account deletion is a "Data Residue" failure. This is not a "choice"—it’s technical negligence.
2. THE "INTENTIONAL" ARGUMENT IS FLAWED: If x10Hosting is intentionally leaving orphaned records to "prevent abuse," they are effectively polluting their own IP space (198.91.80.155) with dead configurations. This is an amateur way to manage a network. A professional system uses blacklists, not "Zombified Configurations" that block legitimate future system resources.
3. LEGAL ESCALATION: You ask what "right" I have?
I have the right to report the mismanagement of .MX resources. NIC México has officially accepted the case (Tickets #MA500319083, #ML100319082). They do not care if the service is free or paid; they care about the integrity of the .MX namespace. If a provider cannot properly de-allocate a .MX subdomain, they are failing their responsibilities as a service provider in that region.
4. THE TECHNICAL DEADLOCK: The domain is "Hard-Locked." This means their automation script is broken. Period. Defending a broken script just because it's a free service shows a lack of technical standards.
I am not asking for your permission to complain. I am documenting a failure that x10Hosting refuses to fix. I will continue to update this thread with the findings from NIC México and ICANN.
Silence from support is not a "policy"—it's an admission of technical incompetence.
Just to clarify for everyone: My goal is a technical fix. I am looking for a manual purge of the orphaned data on server 198.91.80.155 because I want to keep using this infrastructure in a healthy state. I am pushing for professional server maintenance, not a shutdown.
To Bear, dkatsaris, and the rest of the "pro-host" crowd here:
Pro host? Simply applying logic.
Under GDPR and International Data Privacy standards, when a user requests account termination and data deletion, the provider is OBLIGATED to purge all associated records.
If it's linked to you directly. The DNS zone is not that. If this is about GDPR, why go to the .mx registry about it, and instead file a GDPR complaint?
they are effectively polluting their own IP space (198.91.80.155) with dead configurations.
And? It's theirs, to do with as they see fit.
I have the right to report the mismanagement of .MX resources.
This one domain is theirs to use. If they have one or a hundred subdomains, that's up to them. The .mx registry, as far as I know, doesn't regulate internal use of a single domain.
This means their automation script is broken.
That implies you know for a fact there is a script to remove subdomains automatically. I venture to say there isn't, at least not immediately. Again, odds on favorite it's to prevent the removed abuser (assuming) from simply making a new account with that subdomain.
I am not asking for your permission to complain.
No one suggested permission until just now. And us responding is equally allowed here, even if some disagree with you. That's the nature of "discussion".
I try to register it on a completely different account.
As pointed out, multiple accounts aren't allowed there.
One Account
Users may only have active a single account at any given time, signing up for multiple accounts will result in a suspension of service.
Seems you are admitting to violating the terms of hosting with them.
I'd call that a fairly solid reason not to immediately remove DNS records, etc.
- Page :
- 1
- 2
There are no replies made for this post yet.