yesnoox.com

What yesnoox.com looks like right now (from the outside)

If you type yesnoox.com into a browser today, there’s a decent chance you won’t get a normal website. When I tried to load it directly over HTTP, the request failed with a “502 Bad Gateway” response, which usually means the server (or something in front of it) isn’t serving the site properly.

That failure lines up with what third-party domain intelligence pages are reporting: yesnoox.com resolves to an IP address in the 52.213.x.x range and is tied to nameservers that include suspension1.mydomainprovider.com and suspension2.mydomainprovider.com.

Those are not typical nameservers for an active site. They’re commonly seen when a registrar or reseller has moved a domain onto suspension/parking infrastructure.

The “suspension” nameservers and what they usually mean

Seeing suspension1.mydomainprovider.com isn’t proof of anything malicious by itself. It’s a clue about status. WHOIS and DNS ecosystems use patterns, and this is one of them.

A practical explanation: when a domain is suspended (for example, because the registrant didn’t complete contact verification, or because of an abuse workflow, or because of account or billing issues), DNS can be swapped to a controlled set of nameservers. Namecheap’s documentation describes this exact mechanism: the DNS changes, and the website/email services become inaccessible while the issue is unresolved.

On top of that, the nameserver hostname itself maps to an IP address that’s shared across many domains, which is what you’d expect from a suspension or parking setup rather than a dedicated production host.

“Expired” vs “not loading” vs “suspended”: why people mix these up

One reason yesnoox.com is confusing to talk about is that different tools use the word expired differently.

Some “site info” pages label a domain as expired when:

• the website content is gone,
• the hosting is suspended,
• the domain is on parking/suspension nameservers,
• or they infer expiration from signals like default nameservers.

At least one domain profiling page describes yesnoox.com with language like “has expired” while also listing an expiry date in the future, which suggests the label is more about “site not active” than “domain registration ended.”

So if you’re trying to answer the basic question, “Is this site alive?” the cleanest signal is still the simplest one: can it load? Right now, it’s failing to load normally.

What yesnoox.com appears to have been intended for

Some domain-summary services describe yesnoox.com as a “yes/no” style decision website: you ask a question and it returns a binary answer. That kind of site is common because it’s easy to build, easy to share on social platforms, and it doesn’t require ongoing content updates.

Important detail, though: I can’t confirm the on-page experience directly because the site isn’t serving content reliably right now. So treat any “what it does” description as second-hand.

Safety and privacy considerations if you still want to visit

When a domain is unstable, parked, or flipping between states, you should assume the risk profile is higher than normal. Not because it’s automatically dangerous, but because you don’t know what you’ll land on from one day to the next.

A few concrete points to watch:

• Transport security (HTTPS): One checker flags that the site is served over HTTP (no TLS/SSL). If that’s accurate at the moment you visit, anything you type can be intercepted on hostile networks.
• Redirection behavior: Suspended or parked domains sometimes redirect users through ad or tracking chains. If you see unexpected redirects, close the tab. (Also, don’t install anything offered by a random redirect page.)
• Permissions prompts: If the page asks for push notification permission, clipboard access, or unusual browser permissions, that’s a reason to leave.
• “Download to continue” pages: A yes/no prompt site should not require downloads. If it does, treat it as a hard stop.

If you’re just curious, use a safer workflow: visit from a modern browser with tracking protection on, don’t sign in to anything, and don’t reuse passwords. If you need deeper inspection, security teams typically use URL scanning sandboxes (for example, urlscan.io as a general concept) rather than opening suspicious sites directly on a personal device.

If you own yesnoox.com or manage it, what to check first

If you’re on the operator side (domain owner, developer, or reseller), you can usually narrow this down quickly:

1. Check registrar status and notices. Domains can be placed into suspension when WHOIS contact verification is incomplete or contact details changed and weren’t re-verified.
2. Confirm nameservers at the registrar. If you didn’t set “suspension1/2.mydomainprovider.com,” something upstream did it (registrar/reseller/hosting provider).
3. Review billing and renewal. Even when a domain is registered, the website can still be down because hosting was cancelled, a reverse proxy subscription ended, or the origin server was terminated.
4. Look at origin health. A 502 often points to a broken origin upstream of a proxy (crashed app, misconfigured Nginx, dead container, incorrect upstream).

It’s also worth knowing what MyDomainProvider is: it’s a privacy protection service used to keep registrant identity private, with an abuse-report and contact-forwarding process. That can be normal. It can also make it harder for outsiders to understand who runs the site.

Key takeaways

• yesnoox.com is not reliably reachable right now; direct access attempts can fail with a 502 Bad Gateway.
• DNS/WHOIS signals point to suspension infrastructure (suspension1/2.mydomainprovider.com), which is commonly associated with domains that are parked or suspended rather than actively hosted.
• Some sources describe it as a “yes/no answer” decision site, but that’s second-hand while the site isn’t serving stable content.
• If you visit anyway, avoid downloads, permissions prompts, and any page that tries to funnel you through unexpected redirects.
• If you manage the domain, start with registrar notices (WHOIS verification/suspension), then nameservers, then hosting/origin health.

FAQ

Is yesnoox.com a scam?
There isn’t enough direct evidence in what’s publicly accessible right now to label it definitively. What is clear is that the domain is not behaving like a stable, actively maintained site, and it’s tied to suspension-style nameservers, so caution is reasonable.

Why would a domain be placed on “suspension” nameservers?
Common reasons include WHOIS contact verification not being completed, billing issues, abuse handling, or account-level restrictions. Some registrars describe this flow explicitly: DNS changes and services go offline until the issue is fixed.

Does “502 Bad Gateway” mean I got hacked by visiting?
No. A 502 is mainly a server-side failure (proxy can’t reach the upstream, upstream crashed, misconfiguration). It doesn’t automatically mean malware. It does mean the site isn’t functioning normally.

Is it safe to type personal questions into a yes/no site like this?
Even if the site is benign, treat anything you type into random websites as potentially logged. If the site is running without HTTPS, assume network observers could read it.

If I own the domain, how do I get it back online?
Start with your registrar dashboard and email: look for verification requests or suspension notices, confirm nameservers are set to your intended DNS, then verify your hosting/origin is alive and correctly configured. The WHOIS verification suspension flow is a common one.