<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog on RestEpp — REST for EPP domain registries</title>
    <link>https://restepp.dev/blog/</link>
    <description>Recent content in Blog on RestEpp — REST for EPP domain registries</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 02 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://restepp.dev/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Generate a typed .ng domain client in 5 minutes</title>
      <link>https://restepp.dev/blog/generate-a-typed-ng-domain-client-in-5-minutes/</link>
      <pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://restepp.dev/blog/generate-a-typed-ng-domain-client-in-5-minutes/</guid>
      <description>RestEpp&amp;rsquo;s API is defined by a single OpenAPI 3 spec. Point any OpenAPI codegen at it and you have a typed client — here&amp;rsquo;s the fastest path with openapi-typescript.</description>
    </item>
    <item>
      <title>From 4 round-trips to 1: warm EPP pooling on serverless</title>
      <link>https://restepp.dev/blog/from-4-round-trips-to-1/</link>
      <pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://restepp.dev/blog/from-4-round-trips-to-1/</guid>
      <description>Login-per-request against an EPP registry costs seconds. We measured 10.9s cold vs. 1.0s warm with a per-credential connection pool — here&amp;rsquo;s how it works on a stateless function runtime.</description>
    </item>
    <item>
      <title>Your registry password never touches our database</title>
      <link>https://restepp.dev/blog/registry-password-never-touches-our-database/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://restepp.dev/blog/registry-password-never-touches-our-database/</guid>
      <description>How RestEpp API keys encode your EPP credential with AES-256-GCM instead of storing it — tamper-evident, one key per registry, and gone the moment you revoke it.</description>
    </item>
    <item>
      <title>EPP is stuck in 2004 — so we wrapped it in REST</title>
      <link>https://restepp.dev/blog/epp-is-stuck-in-2004/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://restepp.dev/blog/epp-is-stuck-in-2004/</guid>
      <description>RFC 5730 is 20 years old, XML-over-TLS, and stateful. Every registrar-facing integration re-solves the same plumbing problem. Here&amp;rsquo;s why we built RestEpp instead of another one-off client.</description>
    </item>
  </channel>
</rss>
