.PAY domain
Already registered
Looks like a short dictionary-style label with no single obvious trademark match. It could fit multiple brands or products, so the registrant is unclear and confidence is low.
No RDAP data cached yet — click Refresh to pull live records from the .PAY registry.
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.
An ecommerce or gateway business using a payment processor may be closer to the LRP1 eligibility concept, but the registry rules still control. Start at domain.pay to choose the correct path and verify current requirements: https://domain.pay/register. Separate licensing issues remain legal questions.
Yes. You can pre-order vari.pay alongside a backup .PAY name in case vari is allocated to someone else, improving your odds of securing at least one. Browse alternatives near vari at https://domain.pay/domains, then pre-order both at https://domain.pay/register.
.PAY Sunrise is a Start-Date Sunrise, so eligible trademark registrations are allocated on a first-come, first-served basis when policy requirements are met. Start the request at domain.pay: https://domain.pay/register. Waiting can increase the risk that another eligible party gets the matching label first.
Yes. vari.pay is a clear, friendly address for tips, gratuities, or pay-what-you-want pages where you want people to send money easily. The .PAY suffix tells supporters of vari exactly what to do. You can set this up after registering at /register.
Current ICANN dates: .PAY Sunrise is April 13–July 20, 2026; LRP1 is July 20, 2026–February 1, 2027; Trademark Claims is February 1–May 2, 2027. For registration or pre-order action, use domain.pay: 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.