pxmome[.]com Offline: Confirmed Outcome in 18.3 Hours

Case overview

The case concerning pxmome[.]com opened on October 12, 2026, at 15:35 UTC. The site was recorded offline on October 13, 2026, at 09:52 UTC, with an elapsed time of 18.3 hours. Its recorded status is resolved: the reported content was offline, and that outcome was confirmed.

The hosting provider listed for the case is CLOUDFLARENET-EU. The registrar is Chengdu West Dimension Digital Technology Co., Ltd. These details identify the infrastructure organizations associated with the record, but they do not, by themselves, establish which organization caused the reported content to become unavailable.

This distinction matters when describing the result. The supported outcome is a confirmed offline site or removed reported content on the site. The record does not establish a particular enforcement mechanism or attribute the change to a specific provider action. Readers can consult the [pxmome[.]com case record](/threat/pxmome.com/) alongside the timeline and scope described below.

Recorded timeline

October 12: The case opens

The recorded opening time is October 12, 2026, at 15:35:07.304035 UTC. This is the starting point for the case timeline. It should be read as the time the case opened, not as a statement about when the site first appeared or when any underlying activity began.

Keeping that starting point explicit makes the elapsed-time figure easier to interpret. The 18.3-hour interval describes the period between case opening and the recorded offline endpoint. It is not a measure of the domain’s total lifetime, nor does it establish how long the reported content on the site had been available before the case opened.

October 13: The offline outcome is recorded

The recorded offline timestamp is October 13, 2026, at 09:52:00.948161 UTC. The case therefore crossed from one calendar day into the next before reaching its confirmed endpoint.

The record gives the opening-to-reported-content-offline interval as 18.3 hours. That figure summarizes the elapsed time, while the timestamps provide the more precise reference points. Both describe the same case progression: an opening on October 12 followed by a confirmed offline outcome on October 13.

The final status is resolved, with the site offline and the outcome confirmed. That supports describing the case as completed on those terms. It does not support expanding the result into a claim about permanent unavailability or every service that might be associated with the domain.

Provider and registrar context

Hosting provider: CLOUDFLARENET-EU

CLOUDFLARENET-EU is the hosting provider named in the case facts. The relevant provider record offers a separate reference point for readers following that infrastructure organization. The broader hosting-provider index is also available for navigating provider records.

A listed provider and a confirmed offline result are two distinct pieces of information. Their presence in the same case does not establish the exact technical step that produced the result. This article therefore identifies the provider without claiming that it removed content, suspended an account, or performed another specific intervention.

That boundary preserves the difference between association and documented action. It is possible to state clearly where the case was attributed at the hosting-provider level while remaining precise about what the outcome record actually confirms.

Registrar: Chengdu West Dimension Digital Technology Co., Ltd.

The registrar listed for pxmome[.]com is Chengdu West Dimension Digital Technology Co., Ltd. This is a separate role from the hosting-provider entry and should remain separate in the account of the case.

The registrar’s presence in the record does not establish that a registration-level measure was responsible for the offline result. The supplied facts support naming the registrar, but not assigning it a particular intervention. Likewise, the confirmed outcome should not be described as proof of a domain suspension when the recorded result is that the reported content went offline.

Reporting responsibility and outcome attribution

Fraudpol reports to providers and registrars; providers act. The team’s role should not be confused with direct control over a third party’s hosting or domain registration. That division of responsibility is important even when a case reaches a confirmed reported content offline outcome.

For this case, the available facts establish the opening time, the listed hosting provider and registrar, the offline time, the elapsed interval, and the resolved status. They do not establish a detailed sequence of provider decisions. A factual account can report the result without supplying an unsupported explanation for it.

Accordingly, the 18.3-hour figure is best understood as the recorded case-opening-to-offline interval. It should not be relabeled as a particular organization’s handling time. Such a label would require a different set of reference points from the ones provided here.

What the confirmed outcome establishes

The central finding is straightforward: pxmome[.]com was recorded offline, and the case outcome was confirmed. This is stronger than a statement that the case merely opened, but narrower than a claim that every related risk or activity ended.

A useful case summary keeps three elements distinct: the recorded timeline, the organizations listed in the record, and the observed endpoint. Here, those elements support a clear account without requiring speculation about technical mechanisms or responsibility for the change.

Readers looking beyond this individual record can browse the case and threat index. For pxmome[.]com specifically, the conclusion remains bounded by the documented facts: the case opened on October 12, 2026, reached its reported content offline endpoint on October 13, and was resolved with that outcome confirmed after a recorded interval of 18.3 hours.