tamar

10 ms·

1.
by tamar 2y ago
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, please try a different connection (e.g. mob
2.
by tamar 2y ago
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 on these posts, as your claim is invalid; the price is just
3.
by tamar 2y ago
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 the Jewish new year and am rushing in preparation for th
4.
by tamar 2y ago
Hello, I represent Namecheap. Have you spoken to support? Do you have a ticket number? If so, can you please provide that to me?
5.
by tamar 2y ago
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 that helps). My guess is our service reported it accidentally
6.
by tamar 2y ago
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 protection due to registry restrictions. These include .
7.
by tamar 3y ago
Super, much appreciated. We'll take a closer look and see what might be happening here, and appreciate your understanding.
8.
by tamar 3y ago
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 assist you, especially to understand why this is impacting you an
9.
by tamar 3y ago
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 when you do.
10.
by tamar 3y ago
Hi there - can you please reply with the ticket number? I work with Namecheap and would like to investigate this further. Thanks so much.
11.
by tamar 3y ago
I can reply. I work with Namecheap. Will reach out to the OP.
12.
by tamar 6y ago
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 the bottom of the queue again which I recognize is
13.
by tamar 6y ago
Me too!
14.
by tamar 8y ago
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 it as available. Can you check the whois and see
15.
by tamar 10y ago
(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 was replying to. As I said, we are working to resp
16.
by tamar 10y ago
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 of mistakes here. That said, as we
17.
by tamar 10y ago
Namecheap made a response here: https://blog.namecheap.com/social-engineering-issue/
18.
by tamar 10y ago
Yes, and this matter has been appropriately handled. We'll be doing a lot more to ensure it doesn't recur.
19.
by tamar 10y ago
It's in the works. We're aware of the request.
20.
by tamar 10y ago
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.
21.
by tamar 10y ago
I'm aware. This is an isolated comment about other security mechanisms that are in place for the user (not for the support staff).
22.
by tamar 10y ago
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 sides.
23.
by tamar 10y ago
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 this since 2009.
24.
by tamar 10y ago
Doh.
25.
by tamar 10y ago
Thanks for edit2 :) I see us having used the word "mistake" many times here! But yes, we apologize that this happened as well.
26.
by tamar 10y ago
OpenDomain - We have apologized, admitted mistakes, and made tremendous internal change to move on for the better. We would not do that or even post here if we didn't care.
27.
by tamar 10y ago
Yes, learning experiences are had when things happen like this. We look to the future, not to the past, to ensure the same mistakes do not recur.
28.
by tamar 10y ago
^^ we'll take it. We've been responding for the last 1+ hour to things in real time across several social networks, so we're a little rushed. But thanks for the role play :)
29.
by tamar 10y ago
Namecheap has security notifications that inform you of login attempts. https://www.namecheap.com/support/knowledgebase/article.aspx...
30.
by tamar 10y ago
That's exactly what I'm advocating. Standardization would expose millions of people to policies that can be exploited in time. It's better for all of us not to know. I know, this is an issue some would disagree with. I do not

More ›