Policy
Use the contact channel for corrections, technical issues, privacy requests or factual feedback about a repair guide.
- include the public page URL
- do not send passwords or private keys
- describe the observed result and expected behavior
What to include in a technical report
Include the public page or report URL, the exact hostname tested, the approximate time of the result, the expected behavior and the specific finding you believe is incorrect. Screenshots can help when they show a public error, but remove account identifiers, tokens and private control-panel data.
Corrections and provider changes
Provider interfaces and required DNS values can change. If a repair guide no longer matches the official provider documentation, cite the provider documentation and identify the outdated step so it can be reviewed under the correction policy.
Do not send secrets
Never send passwords, registrar recovery codes, API keys, SSH keys, private certificate keys, mailbox passwords or other credentials. HostWithShery diagnostics are designed around public configuration and do not need those secrets.
Production contact channel
The deployment must configure and verify the public contact channel before launch. The repository intentionally does not invent an email address that has not been provisioned on the real domain.