Skip to content

update Pidgeon, Pidgeon domain verification: version 2 with groups - #3218

Open
patrickcneuhaus wants to merge 1 commit into
Domain-Connect:masterfrom
patrickcneuhaus:pidgeon-verify-v2
Open

patrickcneuhaus wants to merge 1 commit into
Domain-Connect:masterfrom
patrickcneuhaus:pidgeon-verify-v2

Conversation

@patrickcneuhaus

Copy link
Copy Markdown
Contributor

Description

Version 2 of pidgeon.ai.verify (merged in #3094, live at Cloudflare since 19 November). Each record now has its own groupId: ownership for the _pidgeon TXT that proves the domain, and agent-signing for the pgn2._domainkey CNAME to Pidgeon's DKIM key. A customer can then prove ownership without delegating a DKIM selector; applying without groupId still writes both, as version 1 did. Cloudflare suggested the split when onboarding version 1. The logoUrl moves to a square PNG that is served directly (the old SVG path no longer is), and the description names the groups.

Type of change

  • New template
  • Bug fix (non-breaking change which fixes an issue in the template)
  • New feature (non-breaking change which adds functionality to the template)
  • Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

  • Template functionality checked using Online Editor
  • Template file name follows the pattern <providerId>.<serviceId>.json
  • resource URL provided with logoUrl is actually served by a webserver

dc-template-linter -merge-or-fail -tolerate warn -logos exits 0.

Checklist of common problems

  • syncPubKeyDomain is set
  • warnPhishing is not set alongside syncPubKeyDomain
  • syncRedirectDomain is set whenever the template uses redirect_uri in the synchronous flow
  • no TXT record contains SPF content
  • txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix
  • no variable is used as a bare full record value (pidgeon-verify=%token%)
  • no bare variable is used as the full host label (_pidgeon is fixed)
  • no variable is used in the host field to create a subdomain
  • %host% does not appear explicitly in any host attribute
  • essential is set to OnApply on records the end user may need to modify or remove without breaking the template (the CNAME; the TXT is the verification itself)

Online Editor test results

Editor test link(s):
Test pidgeon.ai/verify example.com/@
Test pidgeon.ai/verify example.com/agents
Test pidgeon.ai/verify example.com/@, group ownership only

@github-actions

Copy link
Copy Markdown

✅ JSON Filename Check Passed

@github-actions

Copy link
Copy Markdown

✅ JSON Schema Validation Passed

@github-actions

Copy link
Copy Markdown

PR Description Check Passed

All required sections are filled in correctly.

Details
  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 10/10 checkboxes ticked
  OK  Online Editor test results: 3 link(s) found
  OK  Template coverage: all 1 template(s) covered
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete, Test links missing

PR description check PASSED

@github-actions

Copy link
Copy Markdown

Linter OK

pidgeon.ai.verify.json

Level Code Note

@github-actions github-actions Bot added the automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC. label Nov 19, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant