Add Ablazgo domain verification template

[wzdave]

Description

Ablazgo (ablazgo.com) is a multi-tenant e-commerce platform for collectibles stores. This template adds a single TXT record for domain ownership verification.

• Provider ID: ablazgo.com
• Service ID: domain-verification
• Record: TXT _ablazgo.{domain} → ablazgo-site-verification={token}
• syncPubKeyDomain: ablazgo.com
• syncRedirectDomain: portal.ablazgo.com

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

Checklist of common problems

• syncPubKeyDomain is set — this is mandatory
• 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 ("v=spf1 ...")
• txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix — N/A, our TXT record uses a unique prefix ablazgo-site-verification=
• no variable is used as a bare full record value — we use ablazgo-site-verification=%token% (prefixed)
• no bare variable is used as the full host label — host is fixed as _ablazgo
• 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 — N/A, verification TXT records are managed by the platform

Online Editor test results

Editor test link(s):
ablazgo.com.domain-verification with domain apex

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

ablazgo.com.domain-verification.json

Level	Code	Note
info	DCTL1021	missing from iana definitions

[github-actions]

PR Description Check Failed

The PR description is missing required elements. Please update it according to the PR template.

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

Labels to add: Test links missing
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete

PR description check FAILED:
  FAIL  'Online Editor test results': no valid editor test link found
  FAIL  Template coverage: ablazgo.com.domain-verification.json: no editor test link found (expected template id 'ablazgo.com.domain-verification')

[wzdave]

Hi maintainers,

The Online Editor at domainconnect.paulonet.eu returns "Invalid ServiceId or ProviderId" when trying to load this template, since it's a new provider/service that doesn't exist in the registry yet.

This appears to be a chicken-and-egg issue — the editor can only validate templates that are already merged. Since this is a brand new provider template, we're unable to generate the editor test links the CI requires.

Could you advise on the correct way to provide test results for new provider templates? Happy to provide any additional verification you need.

Thanks!

[pawel-kow]

Hi maintainers,

The Online Editor at domainconnect.paulonet.eu returns "Invalid ServiceId or ProviderId" when trying to load this template, since it's a new provider/service that doesn't exist in the registry yet.

This appears to be a chicken-and-egg issue — the editor can only validate templates that are already merged. Since this is a brand new provider template, we're unable to generate the editor test links the CI requires.

Could you advise on the correct way to provide test results for new provider templates? Happy to provide any additional verification you need.

Thanks!

Just copy your template into the editor and test the template. Steps are described in README.