What is templates?

0xallam/templates — explained in plain English

Analysis updated 2026-07-29 · repo last pushed 2026-03-30

Audience · developerComplexity · 2/5MaintainedSetup · easy

Mindmap

mindmap
  root((repo))
    What it does
      DNS auto-setup templates
      Supports many record types
      Variables fill per customer
    Template structure
      JSON files per provider
      Named by provider and service
      Describes needed DNS records
    Use cases
      SaaS custom domains
      Email provider setup
      Website builder DNS
    Contributors
      Service providers
      Developers using Domain Connect
      Online editor for testing
    Quality rules
      Cryptographic verification
      Strict variable constraints
      SPF must use SPFM type

mindmap root((repo)) What it does DNS auto-setup templates Supports many record types Variables fill per customer Template structure JSON files per provider Named by provider and service Describes needed DNS records Use cases SaaS custom domains Email provider setup Website builder DNS Contributors Service providers Developers using Domain Connect Online editor for testing Quality rules Cryptographic verification Strict variable constraints SPF must use SPFM type

What do people build with it?

USE CASE 1

A SaaS company submits a template so customers can point custom domains at the platform automatically.

USE CASE 2

An email provider adds a template to let users configure MX and mail authentication records with a couple of clicks.

USE CASE 3

A website builder creates a template so new users get DNS records set up without manual copy-paste.

USE CASE 4

A DNS provider reviews and approves submitted templates to offer one-click domain connections.

What is it built with?

JSONDomain Connect Protocol

How does it compare?

	0xallam/templates	00kaku/gallery-slider-block	04amanrajj/netwatch
Stars	—	—	0
Language	—	JavaScript	Rust
Last pushed	2026-03-30	2021-05-19	—
Maintenance	Maintained	Dormant	—
Setup difficulty	easy	easy	moderate
Complexity	2/5	2/5	3/5
Audience	developer	general	ops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

No runtime setup needed, templates are JSON files authored and validated through an online editor before pull request submission.

No license information is provided in the repository explanation.

So what is it?

This repository collects configuration templates for the Domain Connect Protocol, a standard that lets domain owners automatically set up DNS records for third-party services. When you sign up for a website builder, email provider, or other online service that needs specific DNS entries, these templates tell the protocol exactly which records to create and how to populate them, so users don't have to manually copy and paste values into their DNS dashboard. Each template is a JSON file named after the provider and service (for example, myprovider.com.website.json). The file describes the DNS records a given service needs, things like A records, CNAMEs, MX entries for email, TXT records for verification, and SPF/DKIM/DMARC for mail authentication. Variables in the template get filled in dynamically when a user connects their domain, so the same template works across many customers with different domains and account-specific values. The people who would contribute here are service providers and developers integrating with Domain Connect, say, a SaaS company that wants customers to point their custom domains at the platform automatically. By submitting a template, that company makes it possible for domain owners using participating DNS providers to connect with a couple of clicks instead of manually editing DNS. The README walks contributors through an online editor for building and testing templates, naming conventions, and a detailed set of quality rules. Those rules are notably strict and security-focused. Templates must include cryptographic verification fields so DNS providers can trust them, and there are careful constraints on how variables can be used, for instance, bare variables as full record values are discouraged because they open the door to conflicts or misuse. SPF must use a special SPFM record type rather than raw TXT records, because multiple services' SPF entries need to merge rather than overwrite each other. Contributors must validate with a linter and an online editor before a pull request will even be reviewed.

Copy-paste prompts

Prompt 1

I want to create a Domain Connect template for my SaaS app at myapp.com that sets up an A record and a CNAME for the www subdomain. Help me build the JSON file following the naming and security conventions from the 0xallam/templates repo.

Prompt 2

Walk me through the quality rules from the templates repo for contributing a new DNS template, including how to handle SPF records with the SPFM type and cryptographic verification fields.

Prompt 3

Help me write a Domain Connect template JSON file for an email service that needs MX records, DKIM, and DMARC entries, using variables that get filled in dynamically per customer domain.

Prompt 4

I need to validate a Domain Connect template I wrote. What are the linter requirements and online editor steps I should run before submitting a pull request to the templates repo?

Frequently asked questions