domain.dot

← All .DOT names

.DOT domain

multipass.dot

Premium · Available

Open to everyone

Pre-order — be first in line

from $2,800 + $2,800/yr renewal

Pre-pay to reserve a first-day registration attempt. We attempt to register on the first day of broader availability — projected around February–March 2027.

Pre-order now

Not guaranteed. 100% credit toward another domain (or 80% cash refund) if unsuccessful.

Own a registered trademark? Fast-track today

Register inside the .DOT priority window instead of waiting. Premium retail fees still apply on premium names.

I have a TMCH SMD file

from $3,000 + $2,800/yr renewal

You bring the SMD — we handle the registrar submission during the priority window.

Continue with my SMD

I don't have TMCH/SMD yet

from $5,300 + $2,800/yr renewal

Full priority package — lawyer-supported TMCH submission, SMD issuance, registrar handling.

Continue with full priority

Frequently asked questions about multipass.dot

For online checkout, what .PAY domain style is best for trust and conversion?

merchant.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 do I confirm multipass.dot points to the right server?

Run a DNS lookup for multipass.dot and compare the returned A/AAAA records to your server's actual IPs, then load multipass.dot in a browser. Tools like dig or an online checker show exactly where multipass.dot resolves. If they don't match, correct the records and wait for the TTL to clear.

What characters are allowed in a .PAY domain for BNPL checkout?

.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.

How do I prevent multipass.dot from being indexed during development?

Add an X-Robots-Tag or meta noindex to the staging version of multipass.dot, or block crawlers in robots.txt, and ideally put it behind HTTP auth. Remove these once multipass.dot is ready so search engines can index the live site. Never ship noindex to production by accident on multipass.dot.

Should I defensively register my brand in .PAY for invoice collection?

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.

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.