Namecheap status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Namecheap reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Namecheap users through our website.

• Hosting (57%)
• Domains (43%)

Live Outage Map

The most recent Namecheap outage reports came from the following cities:

City	Problem Type	Report Time
Tuxtla	Domains	29 days ago
Centerville	Hosting	29 days ago
Noida	Domains	1 month ago
Purmerend	Domains	2 months ago
Istanbul	Hosting	2 months ago
Charleston	Hosting	2 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Namecheap Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Polyvalent kaizen 🀄️ (@0xKachi) reported 1 minute ago

  Is namecheap hosting down? My websites won’t load

• 
  Alex 🇵🇸 (@alexjaxuk) reported 3 minutes ago

  @receipts_lol But people are praying attention. I've been a lifelong namecheap customer but after what they did to you guys I've moved everything to porkbun

• 
  Surendar (@Surendar__05) reported 7 minutes ago

  - Claude for coding. ($20/mo) - Supabase for backend. (Free tier) - Vercel for deploying. (Free tier) - Namecheap for domain. ($12/yr) - Stripe for payments. (2.9% per transaction) - GitHub for version control. (Free) - Resend for emails. (Free tier) - Clerk for auth. (Free tier) - Cloudflare for DNS. (Free) - PostHog for analytics. (Free tier) - Sentry for error tracking. (Free tier) - Upstash for Redis. (Free tier) - Pinecone for vector DB. (Free tier) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build. It's not that deep bro.

• 
  Kingsley Ibietela Felix (@Iamkingsleyf) reported 8 minutes ago

  @adahstwt Namecheap, first on the list should never be there

• 
  Mohit (@codewith55) reported 11 minutes ago

  Total monthly cost to run a startup: $20 - Claude = coding ($20/mo)💲 - Supabase = backend (Free)✅ - Vercel = deploying (Free)✅ - Namecheap = domain ($12/yr)💲 - Stripe = payments.(2.9%/transaction)💲 - GitHub = version control (Free)✅ - Resend = emails (Free)✅ - Clerk = auth (Free)✅ - Cloudflare = DNS (Free)✅ - PostHog = analytics (Free)✅ - Sentry = error tracking (Free)✅ - Upstash = Redis (Free)✅ - Pinecone = vector DB (Free)✅ There has never been a cheaper time to build

• 
  Kirtesh (@AKirtesh) reported 12 minutes ago

  My current indie hacker stack in 2026: - Claude for Coding - Stripe for Payments - GitHub for Version Control - Vercel for Deployment - Supabase for Backend - Clerk for Auth - Upstash for Redis - Pinecone for Vector DB - Resend for Emails - Namecheap for Domain - Cloudflare for DNS - PostHog for Analytics - Sentry for Error Tracking You can build and ship a complete startup from your bedroom in 2026. The barrier has never been lower 💪

• 
  🛡️Shir Khorshid Noor Cyber Unit🛡️ (@FriendOfTheInst) reported 20 minutes ago

  Sponsored search results are not a trust boundary. A fake ChatGPT download campaign used brand impersonation, malvertising, shared-link abuse, cloaking, platform-specific payloads, CAPTCHA gating, Electron packaging, JavaScript obfuscation, and staged execution to deliver malware to Windows and macOS users. This is not merely another fake download page. It is a clear demonstration of how attackers exploit trust across multiple layers: • Trusted brand • Trusted search flow • Trusted-looking ad placement • Trusted-looking domain patterns • Trusted UI/branding • Trusted installer frameworks • Trusted code-signing assumptions • Trusted AI platform sharing features What happened: Attackers promoted a fake OpenAI/ChatGPT download experience using the domain: openew[.]app The site copied OpenAI-style branding and offered download paths for: • Windows • macOS • Chrome extension The Chrome extension path linked to a legitimate ChatGPT-related extension, further increasing perceived legitimacy. The Windows and macOS download paths delivered malware. Attackers also abused legitimate ChatGPT shared conversation links, including chatgpt[.]com/s/ pages, to host fake outage or download pages. A link hosted on a trusted domain can still deliver attacker-controlled content to users. The campaign employed cloaking and conditional rendering: automated scanners and analysis tools were shown benign content, reportedly an unrelated AR/VR company site, while real browsers received the malicious ChatGPT-themed download experience. That is the key lesson: A trusted domain, HTTPS padlock, sponsored ad, or polished UI does not equal a safe download. Why this campaign matters: Victims were not browsing dark web forums or downloading cracks. They were searching for a legitimate AI tool. That is why malvertising is effective: it targets high-intent users at the exact moment they are ready to install software. The campaign turned normal user behavior into an initial access path. Windows chain: The Windows payload was distributed as: Chat_GPT.exe Reported SHA-256: 56CC26E88C064B0C423AA8AD6530E58F91D1E4D28FAB1A8BCEDEF16A6582B4D2 Additional reported Windows hash: c9e0e6985dca3a179c9bdea4e7b38f7dc57fe00ecedc2fd634256fc53bf2de2d Important: hashes are useful for triage, not sufficient for defense. Campaigns rotate samples. Hunt behaviorally. Windows technical observations: • Installer built with Inno Setup • Electron-based application • Chromium runtime components • resources\app.asar archive • Large obfuscated JavaScript payload identified as winter.js • Hex-encoded strings • Dynamically resolved functions • Control-flow obfuscation • Event-driven execution • CAPTCHA gating before core behavior • Inner Electron payload (App.exe) launched after installation • PowerShell spawned after CAPTCHA completion Observed PowerShell pattern: -ExecutionPolicy Unrestricted -Command - That trailing dash matters. It suggests commands may be supplied through standard input rather than appearing directly in the process command line. This reduces the value of command-line-only detection and makes process-tree and behavioral monitoring much more important. Static red flags: The filename suggested ChatGPT, but embedded metadata reportedly identified the installer as: PovariEGLESVapp Setup The executable was signed by: F.F.A.P. Hurkmans Beheer B.V. That publisher does not align with OpenAI or ChatGPT. Important reminder: a valid code signature does not mean software is safe. It only confirms that the file was signed by a certificate and has not been modified since signing. It does not establish that the software is legitimate or authorized by the brand it imitates. Additional Windows indicators: • App.exe SHA-256: D9AD44D43E57B870793FA5CF7FB3A813990D0CBD0C7087BDE70A5E61FB1F1FE6 • Unexpected Chromium/Electron profile: %APPDATA%\Satoshi • Additional reported path: %APPDATA%\LeronApplication • Reported Electron/Node capabilities: systeminformation, child_process, os, fs, zip-lib, Those modules indicate a capable execution environment: system discovery, file access, archive handling, process execution, and network communication. macOS chain: The macOS payload was delivered as: ChatGpt.dmg Reported SHA-256: 7E5B708F6659B1FAD3AAE7B589A706434FBF21708AEEC5AF5910189B96E25FEF Additional reported macOS hash: c0919e1999eaee67e67aeda0287722775afb04e9a9a0f727928b4d11265fb70b The macOS malware is reported as Odyssey Stealer, a fork of AMOS / Atomic Stealer. Reported macOS targeting includes: • Browser passwords • Browser cookies • Saved logins • macOS keychain data • Telegram sessions • Cryptocurrency wallet directories • Desktop/Documents files with sensitive wallet/key extensions • Ledger Live • Trezor Suite • Exodus • Electrum • Sparrow The most dangerous macOS behavior: Wallet replacement. The malware reportedly attempts to replace legitimate wallet-related applications with trojanized versions. That means a victim may later open what appears to be their normal wallet app, but actually launch an attacker-controlled version. That is not only credential theft. That is long-tail financial compromise. Infrastructure: Reported malicious domain: openew[.]app Reported infrastructure includes: 144[.]172[.]104[.]205 188[.]137[.]246[.]189 192[.]253[.]248[.]181 172[.]94[.]9[.]250 Infrastructure notes: • Recently registered domain • Namecheap / registrar-servers infrastructure reported • RouterHosting infrastructure reported • Passive DNS linked infrastructure to other suspicious or malicious domains • .app domains require HTTPS, so browsers show a padlock The padlock only means the connection is encrypted. It does not mean the site is legitimate. Detection opportunities for defenders: 1. Newly created executables launched from Downloads, Temp, or other user-writable paths 2. Trusted-brand filenames that do not match embedded metadata 3. Installer publisher mismatch: filename says ChatGPT, signer is unrelated 4. Electron apps spawning scripting engines: powershell.exe cmd.exe osascript bash sh zsh 5. PowerShell with: -ExecutionPolicy Unrestricted -Command - 6. Unexpected Chromium/Electron profile directories, such as: %APPDATA%\Satoshi %APPDATA%\LeronApplication or other anomalous Electron profile paths 7. app.asar archives containing large obfuscated JavaScript bundles 8. CAPTCHA or user-interaction gating before malicious behavior 9. Newly registered domains impersonating major software or AI vendors 10. Users installing software from ads instead of official vendor channels 11. Suspicious wallet-app replacement attempts on macOS 12. Post-install network traffic to low-cost VPS infrastructure 13. Legitimate AI sharing URLs that render fake support, outage, update, or installation pages 14. Download pages that show different content to scanners than to real browsers The key defensive point: Do not build detections only around hashes or static strings. This campaign reduces the value of static analysis through: • Obfuscation • Runtime string construction • CAPTCHA gating • Electron packaging • Conditional execution • Cloaking • Staged payload behavior • Shared-link abuse on trusted domains The better approach: • Behavioral detection • Process-tree monitoring • Parent-child process analysis • Script-engine execution monitoring • Browser/download source telemetry • Application control • Newly registered domain monitoring • Publisher and metadata validation • EDR detections for Electron-to-shell execution • Monitoring for AI-platform shared links used as delivery pages • User training focused on sponsored-result and fake-download risk For users: Only download ChatGPT from official OpenAI channels or the Microsoft Store. Do not install software from ads, mirror sites, download portals, unfamiliar domains, or fake support/outage pages. If you installed a “ChatGPT” app from an ad or unfamiliar page: Use a clean device and: • Sign out everywhere from important accounts • Change passwords, starting with primary email • Rotate API keys, SSH keys, cloud credentials, and tokens • Revoke active sessions for email, GitHub, cloud, Discord, Telegram, crypto exchanges, banking, and password managers • Move crypto funds from a clean device • Do not open Ledger/Trezor apps on a potentially infected Mac • Monitor financial accounts • Reinstall the OS • Notify IT/security immediately if it was a work device For AI vendors and platform owners: This is now part of the product security perimeter. Brand impersonation, malicious search ads, fake download pages, clone domains, and abuse of shared AI content are active distribution channels. Practical controls: • Make official download links easy to find • Monitor sponsored ads for brand abuse • Monitor newly registered lookalike domains • Detect abuse of shared-content features • Run takedowns quickly • Publish clear download guidance • Provide signed-installer verification guidance • Coordinate with search/ad platforms • Alert users when major impersonation campaigns are active Bottom line: Attackers are not just exploiting ChatGPT. They are exploiting the trust, urgency, and confusion around fast-moving AI adoption. Today it is ChatGPT. Yesterday it was another AI tool. Tomorrow it will be the next trending product. The malware can rotate. The domain can rotate. The payload can rotate. The brand can rotate. The infrastructure can rotate. The defensive mindset must rotate too: From: “Is this file known bad?” To: “Is this behavior legitimate for this software, this publisher, this user, this source, and this execution context?” That is the difference between signature-based reaction and modern detection engineering. Analysis draws on reporting from Malwarebytes Labs, Evalian SOC, Push Security, BleepingComputer, CybersecurityNews, and OpenAI documentation. #CyberSecurity #Malvertising #ThreatIntelligence

• 
  مركز مهارات الإبداع للتدريب (@cstcksa) reported 20 minutes ago

  @Namecheap Unfortunately, we have had an extremely poor experience with the current hosting provider. Despite multiple attempts to communicate through email and official support channels, we have received no response regarding our inquiries, technical support requests, or account management matters. The complete lack of communication and customer support has caused significant operational difficulties and has negatively affected the management of our website and educational platform. This level of service raises serious concerns about the provider's reliability, professionalism, and commitment to its contractual obligations. We respectfully request an immediate response to our pending requests and a prompt resolution of all outstanding issues. If the company is unable or unwilling to provide the required support, we request full cooperation in transferring the hosting account and related services to an alternative provider without further delay.

• 
  K S (@kj_kjato) reported 21 minutes ago

  @Namecheap Furthermore, I will explode that you’ve never invested anything and immediately replied that claims are unfounded when clearly they are not. You don’t want me to expose you and your bullshit customer service.😡😡

• 
  Wiz (@wizminar) reported 21 minutes ago

  @kalashvasaniya totally agreed, one crucial advice i can give is to keep domain and hosting service different. Will ideally prefer about it can look namecheap or porkbun for domain and netlify or hostinger for hoosting rest please do your own research

• 
  Akinsete Motunrayo (@Harkinsete) reported 22 minutes ago

  I built my entire personal brand with AI and a clear process. Here is exactly what I built and how I did it, because you can do this too. What I Built ✅ Brand Strategy (mission, vision, values) ✅ Visual identity: colors, fonts, logo, brand guidelines ✅ A full pitch deck (12 slides) ✅ A speaker kit PDF ✅ A complete multi-page personal brand website ✅ A free lead magnet (a guide people can actually use) How I Built the Website Step 1: I planned before I touched anything I wrote down my brand colors, my fonts, my page structure, and what I wanted each page to do. Most people skip this. Everything breaks when you skip this. Step 2: I gave Claude one detailed prompt with my brand colors, fonts, pages, and copy. It returned a complete, mobile-responsive, multi-page website as a single HTML file. One file. Ready to deploy. The prompt I used: - "Build me a complete personal brand website as a single HTML file. Pages: Home, About, Services, Portfolio, Contact. Primary color [your hex], accent color [your hex], background [your hex]. Display font [font name], body font [font name]. Home page needs: dark hero with my name, photo on the right, tagline, and a CTA button. Services section. Impact numbers. Mobile responsive. No frameworks." Copy this, edit your details, and fine-tune as you want. Step 3: I pushed to GitHub: Free. This took me less than five minutes. Now every update I make is version-controlled and safe. Step 4: I deployed to Vercel for free. Connected my GitHub repo to Vercel and the site was live in under few minutes. This requires no hosting fees and nothing to manage. Step 5: I bought my domain on Namecheap - Searched for my full name and found the .com. Bought it for less than $12 for the year. Added it to Vercel. Updated the DNS settings on Namecheap. Waited 20 minutes. My website was live at my own domain. - Total cost: less than $12. - Total time to go live: under 2 hours. I am also working on a mobile app. A Progressive Web App, which means anyone can visit the URL on their phone and add it to their home screen like a real app. I may be running a live training in July where I will walk you through this entire process step by step to build your live website with a custom domain. If you have a phone and a laptop, you can do this. I documented everything the steps, the exact AI prompts, the domain checklist, the deploy instructions in a free PDF guide. Comment BRAND IDENTITY below and I will send it straight to your inbox. 💾SAVE THIS POST. You will want to come back to it. 🔁 SHARE IT with someone who keeps saying they need a website. The only thing standing between you and a professional online presence is the decision to start. Love and Light, Motunrayo 🤍

• 
  Zara_Schneider (@ZSchneider76107) reported 23 minutes ago

  @MacdevM Mostly comes down to control and pricing for me Cloudflare and Namecheap usually stand out for clean management and no unnecessary upsells 🚀

• 
  Bennico (@baro0xx) reported 26 minutes ago

  @Namecheap Fix your servers!!! 33% packet lost to 8.8.8.8 is unacceptable even for a server in Africa. Your tech support telling me to reboot and change hostname. They clueless. This is a serious production software. Fix your servers and educate your tech support!!!

• 
  Johnmark Obiefuna (@jayhemz) reported 28 minutes ago

  @Nueltek a few minor inaccuracies here. > low-traffic websites the hypernova VPS subscription on Namecheap accomodates up to 10TB in bandwidth. that's more than enough for most traffic loads. > if the VPS goes down it's still more reliable than shared hosting > if one website gets compromised, the entire server could be at risk true. only if the exploit gets a hold of 'root' > 1 site experiences a major traffic spike cloudflare to the rescue > single point of failure? cloudflare to the rescue hehe.

• 
  Qirisiti Returns (@QirisitiReturns) reported 30 minutes ago

  @Namecheap upon checking my hosting list there was nothing, talking to support they say that i have been refunded stellar, but there is no confirmation email of that. hmm, on the domain they said it was put on auction and i cant access it or recover it

• 
  anderson (@U__anderson) reported 31 minutes ago

  @John_ACW @Namecheap how many businesses with actually good support can you even name? probably none

• 
  Prashant Singh (@prashant_gigs) reported 31 minutes ago

  I don't know when the domain registrars will understand user experience is as important as your domain service. --- okish -------- - hostinger - godaddy ---- garbage ---------- - namecheap

• 
  OneAndOnlyAarav (@WaterAarav) reported 33 minutes ago

  Claude = coding. ($20/mo) Shypmenta = deploys, connects, and manages every platform below. Basically your Cursor for shipping.($6/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20. Building has genuinely never been this affordable, and rarely this effortless either.

• 
  Alex @Bickov (@bickov) reported 34 minutes ago

  @justbyte_ Namecheap for the cheap first year, then transfer to Cloudflare. Cloudflare is at-cost with no markup, so renewals never jump, about $10.44 for a .com forever instead of ballooning year two. Only catch is you have to use their nameservers.

• 
  Eric (@realfunnyeric) reported 36 minutes ago

  @Dynadot @Namecheap Eh. Gotta be a better way. Everyone trying to hang on to their customers. Taking them hostage. Maybe I’ll build a tool that does it. ¯\_(ツ)_/¯

• 
  DR ALEXO (@DrAlexos) reported 43 minutes ago

  Btw guys, let me share something about Minecraft. If you didn't grow up playing Minecraft on eg McPvP, factions and these other hardcore servers, you will never be successful. Holy ****, do I have connections from those times. On top of that, I just checked, I've had my namecheap and godaddy accounts since 2013, at which point I was 10. The amount of knowledge and experience I have at my age now is unheard of unless you also grew up playing on those servers. Take Malone Lam for example. It also makes me immune to empty threats, mf I was 10 with a ddos software on my iMac, don't think you can intimidate me. Magnum PI couldn't dig up more dirt on somebody than I can. TLDR: Minecraft makes Millionaires

• 
  Qamar Issa (@QamarIssaqf) reported 43 minutes ago

  @0xPurchase @sidomains @NamePros How to buy in less 25$ Which platform bro to invest I search namecheap spaceship not support this

• 
  adas🧦🌹 (@adastroworld) reported 47 minutes ago

  @PersonaIData It’s been like $10 for the past 10 years so not terrible but yeah it’s just my custom email domain from namecheap Cloudflare allegedly cheaper so I’m gonna transfer out

• 
  👑𝘴𝓲ꪶꪶꪗ ᧁꪮꪮ𝘴ꫀ 👑 (@_SILLYGOOSE_ofl) reported 50 minutes ago

  @TheTrunkTales @GunGnome__ @Namecheap That dude sucks **** for bus fare, then walks.

• 
  𝕯𝖊𝖛𝕰𝖓𝖓𝖞 (@ennycodes) reported 52 minutes ago

  📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout

• 
  Phil (@0xPhilH) reported 55 minutes ago

  @milanm_ @levelsio @Cloudflare To add here, since CFs offices are in France, they overcomply with every bs EU request, even if you host a service that is US only. They won't do that for the content part, so namecheap registar + CF dns + CF CDN is actually best of both worlds combo.

• 
  SYL Vexora- Jaron K Bragg (@JaronBragg) reported 57 minutes ago

  @its_sidraa Why not skip namecheap and just use cloudflare for both domain and DNS? Cloudflare actually puts my website on the map. Namecheap I never seen it and was hard for others to surface. Other than that it makes sense.

• 
  Shimazu.S (@ShimazuSystems) reported 57 minutes ago

  @robintel And also IONOS was abysmal for setting up DNS stuff (this is partly on Google/Firebase though), never had this issue with namecheap DNS

• 
  Christine Harrington (@savvysaleslady) reported 59 minutes ago

  My domain was shut down by @GoDaddy on May 10th. No idea why & the domain was paid up for a year back in Feb. 2026. I’ve called twice a day trying to get this resolved with GoDaddy. Absolutely a waste of my time. I moved the domain today to @Namecheap but GoDaddy is now taking 5-7 days to initiate the transfer. I’ve reached out to @GoDaddyHelp numerous times with no response. Can you imagine providing such poor service?

• 
  Nakniki (@Nakniki3) reported 59 minutes ago

  @ronisarkar_exe I’ve found Namecheap has better customer support! Super helpful when issues arise!