Viewing profile — tamar

Hi, everything looks up and running from here. Any ongoing or long term downtime will be posted here: https://www.namecheap.com/status-updates/ If you cannot access the site, pleas…

Again, if you would like to get assistance with this issue, you will need to open a ticket per our policies and I will have this investigated. I will not be able to engage further …

Actually, I did not decide anything was true and opt not to answer. The replies to this comment thread did not notify me for some reason, and further, I'm about to go offline for t…

Hello, I represent Namecheap. Have you spoken to support? Do you have a ticket number? If so, can you please provide that to me?

Hi, Tamar from Namecheap here. This is not a practice we partake in as you can read by the comments. Please share the domain in question via DM (I use the same name on reddit if th…

Hi, Tamar from Namecheap here. It's common for newly registered domain names to be targeted, especially if the WHOIS information is not protected. Some domains do not allow WHOIS p…

Super, much appreciated. We'll take a closer look and see what might be happening here, and appreciate your understanding.

Support is aware of your issue and is awaiting details, and this is now in a specific escalation process to upper management. I will need some information in order to further assis…

If you can open a ticket (via support at namecheap dot com) with details and the domain name, I'll make sure this gets appropriately escalated. Just let me know the ticket number w…

Hi there - can you please reply with the ticket number? I work with Namecheap and would like to investigate this further. Thanks so much.

I can reply. I work with Namecheap. Will reach out to the OP.

Hi, I work with Namecheap. There's an incredibly high load on the ticketing system right now and unfortunately it's designed that replies to tickets ends up bumping the ticket to t…

Me too!

Hi guys - I work for Namecheap. We don't own any call centers. We don't even offer phone support. It sounds to me like the domain may have been premium and we accidentally reported…

(the reply link didn't show up before, so I don't know if you saw my response posted right after this) To be fair, your third edit was only for me. And that was the only comment I …

Let's not throw personal attacks at me (and the tongue-in-cheek "congrats for being promoted to executive!" comment). There's plenty of remorse and there's plenty of acknowledgment…

Namecheap made a response here: https://blog.namecheap.com/social-engineering-issue/

Yes, and this matter has been appropriately handled. We'll be doing a lot more to ensure it doesn't recur.

It's in the works. We're aware of the request.

Sure it does. People in positions like this are required to learn. If they repeat serious mistakes like this, they're not the right fit for the job.

I'm aware. This is an isolated comment about other security mechanisms that are in place for the user (not for the support staff).

skj, there's a lot more to policy and procedure than just human intervention. We're fully aware of this valid concern and are committed to security on both human and technical side…

We're always keeping tabs on what's going on - it's called taking care of our customers and making sure we learn from our mistakes. This isn't new behavior for us. I've been at thi…