.PAY domain
Checking availability…
.PAY labels must follow registry label rules, including 1–63 characters, letters, numbers and hyphens, no leading or trailing hyphen, and additional IDN/reserved-name rules. Test the exact label at domain.pay: https://domain.pay/register. Technical validity does not guarantee availability.
For a blocked testkes.pay, the lookup indicates it's off-limits per Amazon Registry Services and not registrable, distinguishing it from reserved or taken. You'll also see alternatives to testkes. Run the lookup for testkes.pay — status can change — at https://domain.pay/domains.
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.
Yes. Dedicate a subdomain such as api.testkes.pay with its own DNS record and SSL, and serve your endpoints there. Using testkes.pay for APIs keeps a clean, branded base URL for integrations and webhook callbacks. Secure it with HTTPS and proper auth.
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. Treat this as domain-registration guidance, not legal advice on money-transmission or financial-services licensing.
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.