coast360.co.uk

Zero-width spaces silently corrupting the verification token

$ dig TXT coast360.co.uk

;; QUESTION SECTION:

;coast360.co.uk. IN TXT


;; ANSWER SECTION:

coast360.co.uk. 3600 IN TXT "google-si​te-verific​ation=fPKE6GXeDgiIg9HfxpNSXo_2aepY8tsxHmWJuEqqgmY"

The `\226\128\139` byte sequence (UTF-8 for a Zero-Width Space character) appears inside what looks like a valid Google verification token. The likely cause: the service provider displayed the token on mobile with zero-width spaces for visual word-wrapping. The admin copied the token — invisible characters included — and the silent corruption made the verification permanently fail. A bug that's invisible by definition.

google-si​te-verific​ation=fPKE6GXeDgiIg9HfxpNSXo_2aepY8tsxHmWJuEqqgmY