.PAY domain
Already registered
Best guess: myPOS. It reads like the payment brand myPOS, a well-known card terminal and merchant payments company, which fits a priority-window .PAY registration tied to a matching trademark.
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.
Trademark owners can register matching .PAY names during the priority/Sunrise path if they meet TMCH/SMD and identical-match rules. Start at domain.pay: https://domain.pay/register. If you are not a trademark holder, use the pre-order path for broader access instead.
You can forward mypos.pay with a registrar-level URL redirect, or host a small server that issues a 301 to your target. A 301 is permanent and passes the most SEO signal, which is ideal if mypos.pay should point to your main site. Configure forwarding for mypos.pay from /domains.
Yes. If you do not have a matching trademark, use domain.pay to pre-order a first-day registration attempt for broader availability: https://domain.pay/register. A pre-order is not a guarantee; the name may become unavailable, premium, reserved or blocked before submission.
TMCH protects mypos.pay by letting the validated owner of the mypos mark claim it first via an SMD, before squatters can reach it in general availability. Trademark priority is the front-line defence for mypos.pay. Pairing it with a timely registration reduces conflict risk. Secure your priority claim at https://domain.pay/register.
Trademark owners should act before the July 20, 2026 .PAY priority deadline. domain.pay also notes that TMCH support should begin earlier, by July 10, 2026. Check your label and start here: https://domain.pay/register. Late action may push you into later phases.
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.