https://web.plc.directory/

1<!doctype html>
2<html lang="en">
3<head>
4  <meta charset="utf-8">
5  <meta name="referrer" content="origin-when-cross-origin">
6  <meta name="viewport" content="width=device-width, initial-scale=1">
7  <link rel="stylesheet" href="/static/pico.min.css">
8  <title>did:plc Directory</title>
9  <style>
10html { position: relative; min-height: 100%; height: auto; }
11body { margin-bottom: 3em; }
12body > nav { background-color: var(--muted-border-color); }
13body > footer { position: absolute; bottom: 0px; padding: 2em; background-color: var(--muted-border-color); }
14thead th { font-weight: bold; }
15main article { margin: 2.5rem 0; padding: 2rem; }
16
17/* Green Light scheme (Default) */
18/* Can be forced with data-theme="light" */
19[data-theme="light"],
20:root:not([data-theme="dark"]) {
21  --color: black;
22  --primary: #3949ab;
23  --primary-hover: #3f51b5;
24  --primary-focus: rgba(57, 73, 171, 0.125);
25  --primary-inverse: #FFF;
26  --code-color: var(--color);
27}
28
29/* Green Dark scheme (Auto) */
30/* Automatically enabled if user has Dark mode enabled */
31@media only screen and (prefers-color-scheme: dark) {
32  :root:not([data-theme]) {
33    --color: white;
34    --primary: #3949ab;
35    --primary-hover: #3f51b5;
36    --primary-focus: rgba(57, 73, 171, 0.25);
37    --primary-inverse: #FFF;
38    --code-color: var(--color);
39  }
40}
41
42/* Green Dark scheme (Forced) */
43/* Enabled if forced with data-theme="dark" */
44[data-theme="dark"] {
45  --color: white;
46  /* --muted-color: white; */
47  --primary: #3949ab;
48  --primary-hover: #3f51b5;
49  --primary-focus: rgba(57, 73, 171, 0.25);
50  --primary-inverse: #FFF;
51  --code-color: var(--color);
52}
53
54/* Green (Common styles) */
55:root {
56  --form-element-active-border-color: var(--primary);
57  --form-element-focus-color: var(--primary-focus);
58  --switch-color: var(--primary-inverse);
59  --switch-checked-background-color: var(--primary);
60}
61  </style>
62  
63  
64  
65  
66  <meta name="application-name" name="DID PLC Directory">
67  <meta name="generator" name="webplc">
68</head>
69<body>
70<nav class="container-fluid">
71  <ul>
72  	<li><a href="/"><strong>did:plc</strong></a></li>
73  </ul>
74  <ul>
75  	<li><a href="/resolve" >Lookup</a> </li>
76  	<li><a href="/api/redoc" >API</a> </li>
77  	<li><a href="/spec/v0.1/did-plc" >Specification</a> </li>
78    <li><a href="https://github.com/did-method-plc/did-method-plc">Code</a></li>
79  </ul>
80</nav>
81
82<main class="container">
83  <hgroup>
84    <h1>DID PLC Directory</h1>
85    <h3>A self-authenticating Decentralized Identifier (DID) system which is strongly-consistent, recoverable, and allows for key rotation</h3>
86  </hgroup>
87
88  <p>PLC is a persistent global identifier system, which allows accounts to retain relationships while changing names or migrating between service providers. It uses cryptography to gives individuals (or organizations) direct control and ownership over their identitifier. It does not make use of any blockchain or cryptocurrency technology, and is inexpensive enough to provide as a no-cost service.</p>
89
90  <p>PLC stands for "Public Ledger of Credentials". The system implements the W3C Decentralized Identifier (DID) standard. This makes it interoperable and reusable by other applications and organizations.</p>
91
92  <p>The DID PLC system was originally developed in 2022 by <a href="https://bsky.social">Bluesky Social PBC</a> to support AT Protocol (<a href="https://atproto.com">atproto</a>). They wanted a strongly consistent, highly available, recoverable, and cryptographically secure method with fast and cheap propagation of updates. Since then over 40 million atproto account identifiers have been registered.</p>
93
94  <p>In 2026 the <a href="https://plcred.org">PLC Organization</a> was founded to be a neutral steward for the DID PLC system. The system may evolve to add functionality or improve security, but will do so in a backwards-compatible manner so that existing DIDs will continue to resolve.</p>
95
96  <article>
97    <h3>For Developers</h3>
98    <p>DID resolution can be as simple as:
99    <pre><code>curl -s "https://plc.directory/did:plc:ewvi7nxzyoun6zhxrhs64oiz" | jq .</pre></code>
100    <p>Jump in to the <a href="/spec/v0.1/did-plc">specification</a> to understand how to verify self-certifying operation logs.
101    </p>
102    <p>Check out the <a href="/api/redoc">HTTP API documentation</a> (generated from an OpenAPI schema) for details on how to submit operations, fetch the current DID document, or get a paginated export of all operations for all accounts.</p>
103  </article>
104</main>
105
106<footer class="container-fluid">
107	<div class="container">
108    <small>Developed by <a href="https://bsky.social">Bluesky Social PBC</a> for <a href="https://atproto.com">atproto</a></small>
109  </div>
110</footer>
111</body>
112</html>