Four more dns.TXT verification tokens below the ten-link bar: Dell Technologies, Gather, Mosyle, CAF

[cristianovisk]

Four further providers have self-identifying dns.TXT verification tokens, but each was
observed on too few domains in my corpus to meet the ten-link bar in CONTRIBUTING.md, so I am
raising them here rather than in a pull request.

Corpus: 6128 TXT records from 178 mutually independent apex domains, resolver 1.1.1.1. Zero false
positives for all four patterns.

Proposed technology	dns.TXT pattern	Domains	Suggested cats
Dell Technologies	dell-technologies-domain-verification=	4	19 Miscellaneous
Gather	gather-domain-verification=	3	19 Miscellaneous
Mosyle	^Mosyle-verification-\d+$	1	16 Security
CAF	caf-verification=	1	69 Authentication

Observed domains, and one real sample value each:

• Dell Technologies — adyen.com, amazon.com, ifood.com.br, nytimes.com

  dell-technologies-domain-verification=adyen.com_b9f0f1e6-c2c4-4520-9df4-ff8fe040826b_17351…
  

• Gather — ifood.com.br, twilio.com, vercel.com

  gather-domain-verification=de75674f-d865-405f-95c1-7d98f3100701
  

• Mosyle — ifood.com.br

  Mosyle-verification-1743799440
  

• CAF — ifood.com.br

  caf-verification=370f18bb383afa1e4ebf2eaf5c6ebaf73d2bc7364f91541528466798b3111acf
  

Two questions for maintainers:

1. Is the ten-link rule a hard bar for dns.TXT fingerprints specifically? A verification token is
   self-identifying in a way a scriptSrc pattern is not, and measured on this same corpus the
   catalog already carries loom-verification (4 domains),
   windsurf-verification= (4) and
   heroku-domain-verification (0).
2. If you would rather see wider corroboration first, I am happy to extend the corpus and come back
   with a pull request for whichever of these clear the bar.

Note: Mosyle uses a - separator rather than =, hence the anchored form ^Mosyle-verification-\d+$.