Colon is almost certainly a data artifact in the NYC or Seattle pet licensing registry — a punctuation mark, data entry error, or field separator that got captured as a pet name. At rank 2884 with 30 total counts, it has no plausible path as an intentional pet name choice in the usual sense.
The Registry Artifact Problem
Open government licensing datasets are rich with these entries. A colon character used as a field delimiter, a data entry mistake, or a form submission glitch can end up recorded as a dog's registered name. This happens regularly in large municipal datasets where human review is minimal. The name appears neutral in the gender_pref column, consistent with non-human-origin data.
What the Data Actually Tells Us
Finding Colon in a pet name list is useful for one thing: it shows how raw licensing data, when used directly for pet name rankings, occasionally surfaces these artifacts. Dedicated data cleaning can catch obvious punctuation but misses entries like this that look like a valid string. If you're browsing for actual name ideas, names like Conor or Cosmo are what owners in this initial-C zone are actually choosing.
The Counter-Reading: Accidental Conceptualism
There is, theoretically, an owner out there who named their pet Colon with full awareness — perhaps a punctuation enthusiast, a typographer, a writer with a very dry sense of humor. If that person exists, they have our respect. Most of the 30 entries in this record are probably not them.