Additional info: in Railway → Public Networking, the custom domain is listed as:

wcore.xyz

Port 8080

Status: Waiting for DNS to propagate...

It has been stuck in this state for about 2 hours.

Since public resolvers still return NXDOMAIN and RDAP shows server hold, it looks like the domain is not just waiting for DNS propagation, but blocked at the registrar/registry level.

The serverHold on wcore.xyz was placed by the .xyz domain registry, not by us or name.com. Since the domain was purchased through us, we can reach out to the registrar on your behalf to request the hold be lifted. Before we do, could you share what exactly was hosted on this domain? That context will help when we contact them.

Hi Mykal, thanks for offering to reach out.

wcore.xyz hosts WCORE, a free, non-custodial, multi-chain wallet analytics tool covering 180+ chains across EVM, Solana, and Cosmos. Core features:

• Read-only portfolio tracking (paste an address or optionally connect a wallet via wagmi, RPC queries only)
• Pricing cascade from public APIs: DefiLlama, DexScreener, GeckoTerminal, Jupiter, CoinGecko
• Built-in scam-token detection (7-rule engine) to protect users
• Optional "on-chain GM" social feature: users can deploy their own tip contract on supported chains, everything is transparent and user-initiated

Stack: Fastify + Prisma + PostgreSQL + Next.js 16 + Redis, deployed on Railway. Public presence: @WCORExyz on X.

I received no notification before the hold. If the .xyz registry can share the specific report or reason, I'll gladly provide any clarification needed.

Thanks for the detailed write-up on WCORE, that's helpful.

To set expectations: the serverHold on wcore.xyz was applied by the .xyz registry, and it's not something we or Name.com can lift through normal domain controls. That hold also pulls the domain from DNS at the registry level, which is exactly why it returns NXDOMAIN and why the Railway dashboard is stuck on "Waiting for DNS to propagate." That status will clear on its own once the hold is lifted, so there's nothing to change in your Railway settings right now.

What we're doing: we're opening a request with the registrar to get the specific reason for the hold and what's required to remove it. Holds like this are usually tied to an abuse or verification review, so their reply may ask for more detail about the site.

Two things on your end that may help in the meantime:

1. Since Railway is listed as the registrant contact on domains purchased through us, any verification or notice emails from the registry would have gone to our side rather than yours. We'll check for those as part of our outreach. That said, if you received anything from the .xyz registry or Name.com at the email you used to sign up, it's worth checking.
2. Have your WCORE documentation handy (that it's non-custodial, read-only, how the tip contracts work), in case the registry asks for it.

We'll follow up here as soon as we hear back. Thanks for your patience.

Thanks. Please ask the registrar/.xyz registry what exact requirement triggered the serverHold and what is needed to remove it.

WCORE is still in development. The portfolio scan is read-only: users paste a public address, and the app queries public RPCs and price APIs. No wallet connection, signature, custody, deposits, swaps, or approvals are required.

Wallet connection is only for an optional GM tip-contract feature initiated by the user.

Quick question: why is this thread marked "Awaiting User Response"?

From my read of your last message, the next action is on your side

(opening the request with the .xyz registry and waiting for their reply).

I have nothing actionable to add until you hear back from them.

Let me know what specific input you're waiting on from me?

Sorry for the confusion. That was just to signal (to ourselves) that we don't have anything to do on this at the present. We are tracking the resolution for wcore.xyz and will notify you here when it is resolved.

Hi, following up on this one. It has been a few days since the last update, so I wanted to check whether the registrar or the .xyz registry came back with the specific reason for the serverHold and what is required to lift it.

A rough timeline would help a lot on my end, since wcore.xyz has now been unreachable for over a week and I cannot point anyone to the site. If it turns out the hold cannot be lifted within a reasonable window, I would also like to understand my options for the domain, including a refund. Thanks for staying on it.

Apologies for the delay. We don't have an update from the registrar yet, and I understand this is frustrating with the domain down for over a week. We've escalated the outreach to Name.com and the .xyz registry internally to get a concrete answer on what triggered the hold and what's needed to lift it. Regarding a refund on the domain purchase, if the hold ultimately can't be resolved, that's something we can look into. We'll follow up here as soon as we have a response from the registry side.

Hi, following up again as another few days have passed with no concrete update.

I want to be honest about where I stand: I am strongly disappointed with how this is going. I chose Railway specifically because it promised a single, centralized, and affordable way to take my project to production: hosting and domain in one place, with the simplicity that comes with that. Instead, the domain I purchased through you has been unreachable for over a week, the registrar contact is on your side rather than mine so I cannot act on this directly, and after multiple rounds I still do not have the one thing I keep asking for: the specific reason for the serverHold and what is required to lift it.

I understand the hold itself was placed by the .xyz registry and is outside your normal domain controls. But the registrant relationship is yours, the escalation channel is yours, and right now the visibility and the ability to move this forward sit entirely on your side. That is exactly the part of the centralized model I was paying for, and it is the part that has not delivered.

So I would ask for the following, clearly:

1. A concrete status: has Name.com or the .xyz registry responded to your escalation at all, and if not, when do you expect a reply?
2. The specific trigger for the hold and the exact requirements to remove it, as soon as you have them.
3. A realistic timeline. If you cannot give me a date, please say so plainly so I can plan accordingly.
4. Confirmation of the refund path. You mentioned a refund could be looked into if the hold cannot be resolved. I would like to understand the threshold and process for that now, rather than after more open-ended waiting.

I am not trying to be difficult. I simply need either forward motion or a clear off-ramp, because at this point the domain being down is blocking everything I am trying to build on top of it. Thanks for staying on it.

Apologies for the delay. We don't have an update from the registrar yet, and I understand this is frustrating with the domain down for over a week.

Just to let you know where things presently stand: we reached out to name.com last week and they reached out to the .xyz registry on our behalf. They told us on Thursday they would let us know more when they knew more. We have not heard back from them yet, but I will ask again now for a status update.

We do not have any additional details about the hold, other than name.com told us that .xyz tends to be aggressive with putting on holds and they are likely to want to ultimately hear from you.

Regarding a refund on the domain purchase, I've gone ahead and refunded the $2 charge now, so that should not be a concern. Hopefully we can get this sorted out quickly regardless.

I'm so sorry this process has not gone as it should.

Just heard back from name.com. Apparently the hold has been released. Let us know if you still have issues.