.PAY domain
Already registered
Best guess: generic “subs” is unclear — it could fit multiple trademark holders or a payments/subscriptions product, but there’s no single obvious global brand match from the label alone.
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.
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.
No. VIP handling prioritizes your subs.pay request in our submission queue but cannot guarantee allocation, because Amazon Registry Services makes the final assignment for subs.pay. It maximizes your chances rather than promising the outcome. See what VIP includes at https://domain.pay/pricing.
Yes. A donation platform can use .PAY for a branded payment page if the name is available and registry rules are met. Search the label and choose trademark fast-track or pre-order through domain.pay: https://domain.pay/.
The SMD file is issued by the TMCH after it verifies your rights in the subs mark, and presenting it during priority phases substantiates your claim to subs.pay. It connects your trademark to the registration in a verifiable way. https://domain.pay/pricing
Yes. A wallet or payment app can use .PAY for a memorable payment-specific entry point. Check candidate labels through domain.pay: https://domain.pay/domains. If you own a matching trademark, consider the priority route; otherwise pre-order for broader access.
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.