Add mailblastr.com.domain-verification template (domain ownership TXT)

[shekhu10]

Description

Adds mailblastr.com.domain-verification.json — a Domain Connect template that proves domain ownership for MailBlastr, a developer email platform built on Amazon SES.

It installs a single apex TXT record with a prefixed value:

• @ TXT "mailblastr-domain-verification=%verificationToken%", with txtConflictMatchingMode: Prefix so re-verification updates the existing record instead of duplicating it.

It is a companion to the merged mailblastr.com.email.json (#1292) and the mailblastr.com.mail-send-and-receive.json (#1293). dc-template-linter reports no warnings or errors for this file.

Type of change

Please mark options that are relevant.

• 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?

Please mark the following checks done

• 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 — https://www.mailblastr.com/logo.svg (200, image/svg+xml)

Checklist of common problems

Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.

• syncPubKeyDomain is set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejected
• warnPhishing is not set alongside syncPubKeyDomain — the two must not appear together
• syncRedirectDomain is set whenever the template uses redirect_uri in the synchronous flow
• no TXT record contains SPF content ("v=spf1 ...") — use the SPFM record type instead
• txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix (e.g. DMARC)
• no variable is used as a bare full record value (e.g. @ TXT "%foo%") unless necessary — prefer @ TXT "service-foo=%foo%"; if bare, justify in the PR description
• no bare variable is used as the full host label — the non-variable parts are fixed to limit misuse (e.g. %dkimkey%._domainkey, not %dkimhost%); if bare, justify in the PR description
• no variable is used in the host field to create a subdomain — use the host parameter or multiInstance instead
• %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 (e.g. DMARC)

Notes on the checklist:

• The single TXT uses a fixed @ host and a prefixed value (mailblastr-domain-verification=%verificationToken%) with txtConflictMatchingMode: Prefix + txtConflictMatchingPrefix, so the bare-host, bare-value, subdomain-via-variable, and SPF rules do not apply.
• The record is the template's sole verification record (not a user-modifiable record like DMARC), so essential: OnApply is not applicable.

Online Editor test results

Editor test link(s):

Test mailblastr.com/domain-verification example.com/@

Test mailblastr.com/domain-verification example.com/sub

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

mailblastr.com.domain-verification.json

Level	Code	Note

[github-actions]

Linter passed all checks — approving for auto-merge.

[github-actions]

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: 2 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]

Linter passed all checks — approving for auto-merge.