Sav Official Thread

[Nick R]

Hello NamePros community! We are creating a single thread where we can share announcements in, talk about product updates, people can ask questions and host a great discussion on all things domains!

 

[Future Sensors]

yeah, but the "static" claim next to the rating is now simply false:

The SAV Reviews on TLD-List.com are even worse, with a score of 2.1 out of 5, based on 47 reviews.

https://tld-list.com/registrars/sav

 

[Future Sensors]

As I mentioned here, anyone using SAV should know that if you use SAV, you’re probably not the only one with access to your domain’s functions; previous owners likely still have access too.

That's pretty disturbing.

Tagging @CleanDNS here as well, because they still think that:

Jeffrey Bedser, CEO of CleanDNS, remarked, “I cannot recall a time when a registrar [Sav, red] worked as hard to uphold the security and stability of the Internet in my 15 years with the ICANN community. This proactive approach is setting a new standard in the industry and demonstrates a strong commitment to maintaining a safe and secure internet environment.”

 

[UUnicorn]

Can i use my funds in Sav for domain transfers and new regs?

 

[Future Sensors]

New information is still being added to this thread:

https://www.namepros.com/threads/nameservers-changed-issues-on-sav-com.1331172/

 

[Future Sensors]

 

[Future Sensors]

Sav.com has just fixed a serious bug in their systems.

This bug has been brought to Sav's attention in various ways by other customers in the past, but it wasn't until today that Sav took action, in response to another thread on this forum in which Sav and CleanDNS are being actively discussed.

Let's hope this will be the start of a more proactive approach securing Sav's registrar systems, and keeping the Internet clean from abuse, because Sav is currently scoring poorly in this regard.

It would be recommended that Sav took a more active approach listening to their valued customers. Not only here on this forum, but also on X, other social media, and when customers contact Support directly.

Active participation again in this Sav Official Thread on NamePros could be a start to getting things back on track.

Thanks for fixing the bug today!

 

[Nick R]

Sav.com has just fixed a serious bug in their systems.

This bug has been brought to Sav's attention in various ways by other customers in the past, but it wasn't until today that Sav took action, in response to another thread on this forum in which Sav and CleanDNS are being actively discussed.

Let's hope this will be the start of a more proactive approach securing Sav's registrar systems, and keeping the Internet clean from abuse, because Sav is currently scoring poorly in this regard.

It would be recommended that Sav took a more active approach listening to their valued customers. Not only here on this forum, but also on X, other social media, and when customers contact Support directly.

Active participation again in this Sav Official Thread on NamePros could be a start to getting things back on track.

Thanks for fixing the bug today!

We look forward to engaging more frequently on here as well!

 

[Seventy]

We look forward to engaging more frequently on here as well!

Deep down, Nick, you know exactly what you did.

How about engaging with the costs, stress etc? You are certainly NOT forgiven.

 

[Future Sensors]

Can we also agree that this kind of nonsense will no longer appear on review sites from now on? Please remove all fake Sav reviews, including positive ones that are highly suspicious, or are not even about Sav at all, and remove these nonsense responses by Sav.com. Your 3.1 out of 5 reputation is crap and can only be improved with sincere and serious action. Most can be achieved by just being silent and do your job.

Start today, become a better registrar and start improving your likeability here on this forum and in the cybersec community, where your reputation score is even lower.

Start taking responsibility.

 

[NameGroove]

Hello NamePros community! We are creating a single thread where we can share announcements in, talk about product updates, people can ask questions and host a great discussion on all things domains!

What will your new .com hand reg price be in Sept (after ICANNs price increase)?

 

[Nick R]

Hello. A few notes:

We just posted a large post covering a wide range of topics in the Nameserver thread. Here is a link to it:
https://www.namepros.com/threads/nameservers-changed-issues-on-sav-com.1331172/post-9225539

I specifically want to repost this part of it here:

We are happy to participate in threads that have a clear focus on a Sav-related issue and stay on topic. However, should they be disrespectful, speculative or go wildly off track (like into a company's job postings), will pause our participation and refer people to our very-capable 24/7 support team. That was the case in the past but we are happy to try again.

.COM Hand Reg Prices on Sept 1: As of right now, we are not going to increase the price and will keep it the same at $7.99! That may change if registration volume drastically changes from where it is currently though.

 

[Future Sensors]

You are here on a forum where you cannot influence the responses like you do on Trustpilot and X. I'm very sorry. Everything said here is done with respect and out of genuine concern for the state of Sav, CleanDNS and the security of the Internet and its users. It is now up to you to improve your bad reputation in the cybersecurity community. Sure, you can choose to leave immediately if there is criticism, but you can also think about improving your business.

https://www.namepros.com/threads/sav-official-thread.1202323/page-86#post-9225395

 

[Future Sensors]

@Nick R @Sav.com

It is remarkable that other registrars continue to engage in active and pleasant discussions with members on this forum, and listen to relevant points of substantive criticism that come with it. Always done with the aim of wanting to improve the services of the registrar or marketplace. If this forum could only consist of compliments, no one would come here anymore and it would have no added value whatsoever.

Immediately threatening to leave when there's even a little bit of criticism, that really says a lot about the state of Sav.com at the moment, and the willingness to really want to listen to power users and change the direction of the company.

If you do it right, this forum can benefit you enormously. If you don't want that, feel free to continue on the path you've already taken.

 

[NameGroove]

.COM Hand Reg Prices on Sept 1: As of right now, we are not going to increase the price and will keep it the same at $7.99! That may change if registration volume drastically changes from where it is currently though.

Excellent news! And what will your renewal price for .com be after the ICANN increase in Sept?

 

[Traderas]

@Nick R @Sav.com

Today I noticed 4 domains are missing from my account.
Just 4 random domains, out of the 10,000+ I currently maintain in SAV.

They still seem to be registered in SAV but they are not in my account.
Each of them uses different NS:

ns1-auction.sav.com,ns2-auction.sav.com
augustus.ns.cloudflare.com,laura.ns.cloudflare.com
jm1.dns.com,jm2.dns.com
ns1.dan.com,ns2.dan.com


I contacted support some hours ago, but they were very busy...
The escalated my issue to the developer team...

Now I have 10 open tickets! (some of them 2 months old)

Do I win something?

 

[Nick R]

@Nick R @Sav.com

Today I noticed 4 domains are missing from my account.
Just 4 random domains, out of the 10,000+ I currently maintain in SAV.

They still seem to be registered in SAV but they are not in my account.
Each of them uses different NS:

ns1-auction.sav.com,ns2-auction.sav.com
augustus.ns.cloudflare.com,laura.ns.cloudflare.com
jm1.dns.com,jm2.dns.com
ns1.dan.com,ns2.dan.com


I contacted support some hours ago, but they were very busy...
The escalated my issue to the developer team...

Now I have 10 open tickets! (some of them 2 months old)

Do I win something?

What is your Sav account email address and what are the 4 domain names?

 

[Nick R]

Excellent news! And what will your renewal price for .com be after the ICANN increase in Sept?

10.29

 

[Future Sensors]

Hello All. It seems like we are covering some of the same topics on both thread and our Official thread. I don’t think there is anything new I can share regarding abuse, nameserver changes regarding abuse, expired auctions, our relationship with CleanDNS. Let me answer a few posts from overnight then let's wrap this thread up and continue in here https://www.namepros.com/threads/sav-official-thread.1202323/

@ryan87 – We have gone back and forth on publishing a hard standard of when we move from a domain-level suspension to an account but there are different thresholds where we would take action depending on the domain and the complaint. Take an account that has 2 domains, both CSAM and we get a verified CSAM complaint for 1 of the domains. If we believe the second domain will be used for CSAM as well, we will not hesitate to disable it as well. However, if we are talking about an account with 2 domain names, 1 is used for phishing and one isn’t, we will only disable the phishing domain. We do reach out to all registrants about abuse complaints, regardless of the nature of the complaint. As I have said multiple times before, we would love for this to be moved out of the registrar’s hands and into an independent body overseen by ICANN.

@zotix – Thank you for your business! Regarding data sharing, please see one of my previous posts regarding this. I can tell you that not even Sav has your payment information. Its sent straight to our payment processor, tokenized, and referenced by that token moving forward. No accounts are banned without some communication from us first, we are just going to expand that communication to make it clearer that an account is reaching a number of abuse complaints where if it should continue, we will disable the entire account.

@Future Sensors – Some registries do take an active role in disabling abusive domains, and some rely on the registrar. The registry's actions always supersede ours and we always welcome abuse mitigation from a registry level.

Question 1 – Being a low-cost registrar is usually great, but it does attract a higher level of abuse as well. If you are going to use a domain for abuse, you are going to want to get the best deal on it.

Question 2 – See my long post from yesterday; it covers what we are going to do differently. Regarding estimating the impact – yes, we did. Due to Question 1 above, we did want to make a one-time purge to disable to bad actors who were found to have repeated domain abuse AND ignored our messages to them to try to resolve the abuse. We just should have communicated our actions more clearly and given a last warning.


This will be my LAST post in this thread. We can continue the conversation over in our Official. See you all there.

Thanks for your LAST post @Nick R

Let me be short this time. I sincerely hope that your company Sav.com will soon repair its bad reputation in the cybersec community. Your company is widely regarded as a "high risk" registrar.

I will track this personally, because you know I will not tolerate registrars neglecting to keep our Internet clean.

Wishing you the best of luck with any new methods to combat abuse, but be extremely careful in doing this, and think of registrant rights along the way.

https://www.linkedin.com/posts/renée-burton-b7161110b_challenges-in-measuring-dns-abuse-activity-7126344420802609153-AW84

 

[ryan87]

This is from the other thread.

We have gone back and forth on publishing a hard standard of when we move from a domain-level suspension to an account but there are different thresholds where we would take action depending on the domain and the complaint. Take an account that has 2 domains, both CSAM and we get a verified CSAM complaint for 1 of the domains. If we believe the second domain will be used for CSAM as well, we will not hesitate to disable it as well. However, if we are talking about an account with 2 domain names, 1 is used for phishing and one isn’t, we will only disable the phishing domain. We do reach out to all registrants about abuse complaints, regardless of the nature of the complaint. As I have said multiple times before, we would love for this to be moved out of the registrar’s hands and into an independent body overseen by ICANN.

Thanks for taking the time to reply. My interest is in the broader topic, not just how Sav handles it and your reply helps to illustrate that it's not a simple problem. Everything is subjective and needs to be handled on a case-by-case basis. I agree with that and it's part of what makes it tough from my point of view, especially when the responsibility for interpreting what constitutes abuse is going to vary from registrar to registrar.

It's impossible to have a hard standard because of that and I don't envy the position you're in. I think the conversation gets more productive if others view it in the context of giving you the benefit of the doubt. For example, I don't agree with the sentiment that account bans are part of some grand plan to profit from domain auctions. However, I also don't agree with account bans where registrants don't have a way to mitigate that risk by demonstrating they're trying to be a good faith participant.

I also agree that it doesn't make sense for abuse handling to be the responsibility of registrars. That makes it inconsistent for registrants and I think there's more opportunity to build a better system if abuse handling is done by a third party. I'll explain why I say that...

I think registrars are in the best position to function as advocates for registrants and requiring registrars to act against registrants, even if it's deserved, limits the services that registrars can offer. That deprives registrants of services that could be beneficial to them.

For example, I'll never have the experience or knowledge of someone that's been in the industry for 20+ years. To me, it would make sense to pay my registrar to help me understand and respond to abuse complaints, especially since I'm trying to be a good participant and think handling issues via a cooperative relationship will produce a better outcome for everyone than the current adversarial setup. I also don't do anything that should put me at risk of receiving an abuse complaint, so I have no experience to rely on I ever receive one, which means having someone that can help me if that situation arises would be valuable.

I guess that rounds out the point I was trying to make. If something goes wrong with one of my domains I don't want the system to err on the side of assuming I'm a bad actor and if there were a way to opt-in to a better system that can help indicate I'm a good participant I would do that, even if it costs a bit of money.

I was also hoping to steer the conversation in a more productive direction because I think the original thread had a lot of people that were upset at the idea of being treated like a bad actor rather than being given the benefit of the doubt, but many of them seem to have assumed you're acting in bad faith rather than giving you the benefit of the doubt. I don't think that's fair.

That said, there was one good point raised in that old thread. Having suspended domains end up at auction isn't something that I think should be allowed to happen, regardless of the registrar. It has the potential to create bad incentives. I suspect most of the domains being used for abuse aren't valuable anyway, so maybe it makes more sense to let those drop straight back to the registry. Ideally the registry would hold those for a while to prevent re-registration and to give the original registrant an opportunity to argue they deserve the domain back, but that's something that would have to be required by ICANN.

 

[Future Sensors]

I suspect most of the domains being used for abuse aren't valuable anyway, so maybe it makes more sense to let those drop straight back to the registry.

Sorry, this is far too simplistic. Domain abuse can also occur after a hack has occurred. DNS abuse encompasses a wide range of different types of abuse.