Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Allow using existing `_atptoto.` records for DNS verification

Open
#46 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start by tracing Keytrace's existing DNS verification flow and how it reads TXT records on the root and _keytrace. subdomain. Compare that behavior with ATProto's _atproto. TXT record containing a DID, then add support for recognizing the existing record without requiring a duplicate key. Done means a domain verified through the ATProto record works with Keytrace and existing verification behavior remains intact.

Written by the indexing model from the issue text.

Description

ATProto already has a way for users to verify their domains using DNS, by adding a TXT record containing the DID to an _atproto. subdomain.
Keytrace introduces a duplicate method: a TXT record on the root or a _keytrace. subdomain, containing the DID with a special prefix.
In the spirit of compatibility with the ATProto ecosystem, it would be great to support the existing verification method so people don't have to add a duplicate key just for Keytrace.

Dominant language
TypeScript
Stars
86
Forks
7
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from orta/keytrace

All issues in orta/keytrace

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.