Two instruments that answer a question instead of describing it. No registration, no data leaves the browser.
Five questions at most: what is failing, what has already been tried, and whether the cause sits on the device, at the provider or in the account. The result is an ordered checklist, not a list of guesses.
Type the facts once and get a message with the identifiers, the timestamp and the checks already done — the three things that decide whether a request is resolved in one reply or in four.
The pages on this site explain processes; these tools apply them. The diagnostic orders the checks — because doing them in the wrong order creates new problems, like five code requests triggering a rate limit. The builder turns what the reader knows into what support can act on: an identifier, a timestamp with a time zone, and the checks already completed.
Neither tool asks for a password, a one-time code or a document, and neither sends anything anywhere. That is a design rule, not a limitation: a diagnostic that asks for a code would be indistinguishable from the scams this site documents.