Nameservers Changed Issues on Sav.com

[xmarthost]

My nameservers for all domains have been changed to ns1.all-harmless.domains and ns2.all-harmless.domains, and I am unable to change the DNS again. What could be the issue?

Also, a friend of mine is facing the same problem with over 600 domains. What's going on with sav.com?

 

[bmugford]

Their Final message.

After reviewing your domain portfolio and the abuse reports it has received, we have determined that your portfolio and account present a high risk. We have disabled your domains and locked your account. This decision is final and disabling will not be reversed.

Thank you,
The Sav.com Safety Team

What does this mean exactly?

What does "locked your account" mean?

Can you not even access your account to transfer your domains?

Disabling domains would be bad enough, though likely valid in certain cases.

If the registrar is blocking access to transfer domains, that is basically just theft.

Brad

 

[themuhammadahmed]

What does this mean exactly?

What does "locked your account" mean?

Can you not even access your account to transfer your domains?

Disabling domains would be bad enough, though likely valid in certain cases.

If the registrar is blocking access to transfer domains, that is basically just theft.

Brad

Yes exactly.
They have completely disabled my account, I don’t have any access of my domain portfolio now, all of my domains are suspended and they have not replied to my any email since they changed nameservers of my domains without authorisation.
They just want to sell my premium domains so they can make big bucks.

 

[bmugford]

Yes exactly.
They have completely disabled my account, I don’t have any access of my domain portfolio now, all of my domains are suspended and they have not replied to my any email since they changed nameservers of my domains without authorisation.
They just want to sell my premium domains so they can make big bucks.

It's simply not acceptable for a registrar to lock down domains from the ability to be transferred. @Nick R

If you don't want someone as a customer, that is one thing.

Locking all their domains is way over the line and an abuse of power.

I can't imagine this is allowed under the ICANN transfer policy. It would create such a conflict of interest if a registrar can just seize customer domains, without due process, and potentially profit off them.

Brad

 

[themuhammadahmed]

It's simply not acceptable for a registrar to lock down domains from the ability to be transferred. @Nick R

If you don't want someone as a customer, that is one thing.

Locking all their domains is way over the line and an abuse of power.

I can't imagine this is allowed under the ICANN transfer policy. It would create such a conflict of interest if a registrar can just seize customer domains and potentially profit off them.

Brad

I have mentioned all these things in ICANN complaint. They are investigating the issue and hopefully they will reply soon. I am not very hopeful that they would decide in my favour but really want to see what they do.

 

[bmugford]

I have mentioned all these things in ICANN complaint. They are investigating the issue and hopefully they will reply soon. I am not very hopeful that they would decide in my favour but really want to see what they do.

Private companies can generally choose who they do business with.

However, seizing ALL domains under some abuse complaint goes way too far.

If they don't want someone as a customer, that is even better reason to want the domains to be transferred out.

Instead Sav.com is blocking it from happening? @Nick R

Brad

 

[dirk]

. I am not very hopeful that they would decide in my favour but really want to see what they do.

Don't underestimate yourself. I had a similar issue with directnic years ago.

It took them long enough but eventually they folded after ICANN stepped in and sent me Auth codes to transfer out.

 

[bmugford]

Don't underestimate yourself. I had a similar issue with directnic years ago.

It took them long enough but eventually they folded after ICANN stepped in and sent me Auth codes to transfer out.

ICANN aside, if Sav.com doesn't make some effort to resolve this I will bring the issue to the ICA.

This might not be exactly like the Brent Oxley situation, but it is still a major registrant rights issue if a registrar has the ability to seize ALL domains in an account because of alleged abused.

Even if isolated abuse occurred, the recourse is not to block transfer of ALL domains. That is just taking someone's property.

Brad

 

[dirk]

ICANN aside, if Sav.com doesn't make some effort to resolve this I will bring the issue to the ICA.

Thank you for that and for always watching over us, defending registrant's rights!

If only more pros would care as much as you do.

 

[Future Sensors]

During my career I have been actively involved in combating all kinds of misbehavior at the DNS level. All praise for registrars that actively combat DNS abuse.

It is currently mainly the way in which Sav communicates very poorly about their own mistakes that is causing the company to leave a very bad impression.

And because of @Nick R's most recent posting, this now also reflects negatively on the company @CleanDNS, Inc.

Thanks, Sav.

 

[bmugford]

During my career I have been actively involved in combating all kinds of misbehavior at the DNS level. All praise for registrars that actively combat DNS abuse.

It is currently mainly the way in which Sav communicates very poorly about their own mistakes that is causing the company to leave a very bad impression.

And because of @Nick R's most recent posting, this now also reflects negatively on the company @CleanDNS, Inc.

Thanks, Sav.

I agree. I assume @CleanDNS is providing reports of some kind and then Sav.com is taking action.

While I might have an issue with the accounts being disabled because of abuse, my main concern is related to registrant rights when it comes to blocking access to accounts and therefore being unable to transfer domains.

Brad

 

[CleanDNS]

Hi - Chad from CleanDNS here. Happy to take a look into any account and review the data. Please DM me the email address on the account and I will investigate.

 

[Future Sensors]

Hi - Chad from CleanDNS here. Happy to take a look into any account and review the data. Please DM me the email address on the account and I will investigate.

To all: do not share any data with another entity than Sav.

 

[CleanDNS]

To all: do not share any data with another entity than Sav.

We are the entity that manages Sav's abuse. Feel free to message [email protected] and mention this thread and I'll review that way. Whatever you are comfortable with.

 

[Chris Hydrick]

To all: do not share any data with another entity than Sav.

Why?

 

[dirk]

Why?

For safety concerns?

 

[Future Sensors]

Hi - Chad from CleanDNS here. Happy to take a look into any account and review the data. Please DM me the email address on the account and I will investigate.

You have full account access of Sav customers?

 

[Future Sensors]

This started with a Sav misstep, but it could easily develop into a @CleanDNS misstep, too.

 

[dirk]

This started with a Sav misstep, but it could easily develop into a @CleanDNS misstep, too.

Their domain is registered with sav... Draw your own conclusions...

 

[bmugford]

We are the entity that manages Sav's abuse. Feel free to message [email protected] and mention this thread and I'll review that way. Whatever you are comfortable with.

Who is actually making the decision to block access to accounts and the ability to transfer domains.

Is that you or Sav.com?

Brad

 

[Future Sensors]

@Acroplex
@DomainNameWire
@equity78
@DomainIncite
@ICA

 

[Chris Hydrick]

This started with a Sav misstep, but it could easily develop into a @CleanDNS misstep, too.

How?

Shouldn't those in this thread who have locked domains be happy they now have a POC in @CleanDNS to discuss their issue(s) with?

 

[dirk]

@CleanDNS

Are you owned by/part of constellix?

 

[Future Sensors]

How?

Shouldn't those in this thread who have locked domains be happy they now have a POC in @CleanDNS to discuss their issue(s) with?

You are now going along with Sav's narrative, without perhaps realizing it. Convenient of Sav to delegate it to a new, unaccredited account on this NamePros forum. Sure, just give all your personal information to that account and let the Sav abuse handling take place via DMs on this web forum with CleanDNS. I find it very unwise.

 

[bmugford]

How?

Shouldn't those in this thread who have locked domains be happy they now have a POC in @CleanDNS to discuss their issue(s) with?

But again, what is the exact relationship?

Why does @CleanDNS have access to registrar data?

What data do they have access to?

Who is actually making the decision to lock these accounts?

I mean, at the end of the day it's on Sav.com as they are the ICANN accredited registrar.

Brad

 

[Future Sensors]

Does the Sav privacy policy state that CleanDNS may handle abuse for the company via DMs on an external forum like NamePros?