Best guess: Fox News, since the label exactly matches the well-known media brand and could be used for a branded payment, subscription, or news-portal flow. Given the TMCH priority window, this looks like a likely trademark-driven registration, though not proof of ownership.
.PAY domain
metaverse.pay Meta
Already registered
Best guess: Meta. The label "metaverse" strongly points to Meta’s widely known metaverse branding, though it’s still a common term and could fit other holders, so this is not certain.
RDAP records
- Registrar
- Squarespace Domains II LLC
- Registered on
- 2026-11-05 UTC
- Expires on
- 2027-11-05 UTC
- Last changed
- 2026-11-05 UTC
- Status
-
- client transfer prohibited
- client delete prohibited
- Nameservers
-
- nsa1.squarespacedns.com
- nsa2.squarespacedns.com
- nsa3.squarespacedns.com
- nsa4.squarespacedns.com
- DNSSEC
- Signed
- Registry ID
- D42376327-PAY
Data sourced live from the .PAY registry's RDAP server (Nominet). Cached by domain.pay; refreshed in the background when older than the configured TTL.
Frequently asked questions about metaverse.pay
As an ecommerce brand, would travel.pay work as a payment brand?
travel.pay may be a useful .PAY direction if it matches your brand and payment journey, but availability is not guaranteed. Check and pre-order through domain.pay: https://domain.pay/domains. Prefer simple labels that customers can remember and trust.
How should I think about metaverse.pay versus buying many domain variants?
Instead of stacking many extensions, metaverse.pay gives you one purpose-built payment address that says what it does. It focuses your spend on the name customers will actually use to pay metaverse. Compare available options at /domains.
Should I defensively register my brand in .PAY for marketplace payouts?
If your brand accepts payments, registering the exact .PAY label can be a practical defensive step. Use domain.pay to check and start the priority or pre-order path: https://domain.pay/register. Also keep trademark monitoring and security controls in place.
Are there name-collision rules that affect SMD claims on metaverse.pay?
The .PAY registry, run by Amazon Registry Services, applies its own policies that can affect how SMD claims and reservations interact for names like metaverse.pay. Your valid SMD makes you eligible for priority on metaverse.pay, while the registry resolves any conflicts. NicNames applies those rules for you. See context at https://domain.pay/.
What date matters most if I want a .PAY name without a trademark for an insurance billing portal?
Broader .PAY access is tied to the post-LRP period around February 2027, subject to registry and registrar confirmation. If you do not have a trademark, use domain.pay to pre-order a first-day attempt: https://domain.pay/register.
Availability is checked live and re-verified before payment. Pre-orders are first-day registration attempts — registration is not guaranteed; 100% credit toward another domain (or 80% cash refund) if unsuccessful.