Client certificates are exchanged at onboarding — the port answers to registrars, not browsers.
openssl s_client -connect epp.name.am:700 -servername epp.name.amTHE .AM REGISTRY GATEWAY
The first fully standards-compliant registry gateway for the .am zone — EPP over mutual TLS, WHOIS, and .am's first RDAP. Direct to the registry. $24.00 a year. Transfers free.
$ openssl s_client -connect epp.name.am:700 ✓ TLS established — mutual auth <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <greeting> <svID>epp.name.am</svID> <svcMenu> <objURI>urn:ietf:params:xml:ns:domain-1.0</objURI> <objURI>urn:ietf:params:xml:ns:contact-1.0</objURI> <objURI>urn:ietf:params:xml:ns:host-1.0</objURI> <svcExtension> <extURI>urn:ietf:params:xml:ns:secDNS-1.1</extURI> </svcExtension> </svcMenu> </greeting> </epp> → <domain:check> yerevan.am <domain:name avail="1">yerevan.am</domain:name> 1000 · 38ms
THE ZONE
.am is one of the shortest brand surfaces on the internet — open to anyone, no local presence required. Radio and audio built a culture on it, and a worldwide diaspora keeps it personal. Yet most of the world's registrars still can't sell it.
Until now, the zone had no open, standards-compliant EPP. Offering .am meant proprietary interfaces and one-off workarounds — so most platforms never did. The gateway changes that: the protocols your stack already speaks, pointed at .am.
THE RECEIPTS
Run your conformance suite against it — that's what it's for.
| Standard | What it covers | Status |
|---|---|---|
| RFC 5730 | EPP — protocol core, greeting, session model | ✓ |
| RFC 5731 | EPP domain mapping — create, renew, transfer, info | ✓ |
| RFC 5732 | EPP host mapping — nameservers with glue | ✓ |
| RFC 5733 | EPP contact mapping — real registrant contacts | ✓ |
| RFC 5734 | EPP over TLS — port 700, mutual auth, pinned TLS 1.2+ | ✓ |
| RFC 5910 | DNSSEC — secDNS-1.1, DS data interface | ✓ |
| XSD (strict) | every frame validated against the canonical schemas | ✓ |
| RFC 3912 | WHOIS on port 43 | ✓ |
| RFC 9082/9083 | RDAP — the .am zone's first | ✓ |
| RFC 3915 | RGP — deliberately not offered: .am grants a 45-day flat-price grace window; there is nothing to restore | — |
LIVE
Client certificates are exchanged at onboarding — the port answers to registrars, not browsers.
openssl s_client -connect epp.name.am:700 -servername epp.name.amPort 43, plain and public. The classic query the whole internet still speaks.
whois -h whois.name.am name.amQuery the .am zone's first RDAP right here. Type a name and hit Query.
Try , , or your brand.
HOW IT'S BUILT
Domains are registered to the registrant on record — your customer. Always.
Every inbound frame is validated against the canonical RFC XSDs. Malformed XML gets a clean 2001, not a mystery.
Charge-before-registry, refund-on-failure billing. Every operation lands in an append-only ledger you can export.
Self-service console with balance, ledger, and card refills —console.registry.name.am.
PRICING
Most registrars retail .am at $50 to $110 a year. At $24.00 wholesale, that spread is your margin — far wider than you keep on .com.
One wholesale price for registration and renewal. 1–5 year terms, transfers always free. No setup fee, no minimums, no tiers. Prepaid balance in USD, card refills, and a ledger you can export.
ONBOARDING
Email registry@name.am with your registrar details. A human replies.
You receive EPP credentials; we exchange mutual-TLS certificates and allowlist your IPs.
Run your stack against the OT&E sandbox — register, renew, transfer, poll.
Fund your balance, flip the endpoint, sell .am.
Tell us who you are and roughly how many domains you manage — we'll take it from there.