SITE INFORMATION
Contact Us
Find support and report problems, security issues or content concerns.
Email support
[email protected]Use email for account, privacy, security or content concerns. Keep personal details out of public discussions.
Public issue reports
View and report tool issuesFor public questions and feature requests. Remove passwords, node credentials and subscription secrets first.
Reaching the maintainers
The email address on this page comes from the site's current public settings. Use email for account access, privacy, vulnerabilities and content complaints. For questions and suggestions that can be discussed publicly, use tool feedback or the discussion below the relevant tool or article.
The user guide covers common workflows and troubleshooting. Check the relevant section first. If a report already exists, add reproduction details there instead of opening a duplicate.
Reporting a tool problem
Name the tool, input format and selected output, then describe the expected and actual results. Include the client, operating system and browser versions, the approximate time, and the complete error text.
For a configuration example, replace sensitive values with example.com, documentation IP addresses and invented passwords while preserving the structure that triggers the problem. Subscription secrets, repository tokens, node UUIDs and passwords should not appear in public reports or screenshots. Never send an account password, verification code or two-factor secret for troubleshooting.
Article corrections and broken links
Include the article address, the affected paragraph or link, and what you currently see. Official documentation or reproduction steps are helpful. State the version when a difference between old and current software matters. Applicable corrections keep the original article address so existing readers can find the updated explanation.
Privacy and account requests
Describe account access, profile, correction or deletion requests by email. We may need to verify account ownership to prevent impersonation, but will not ask you to hand over your password or one-time code. The scope of handling follows the privacy policy and available account features.
Security reports
Report vulnerabilities privately. Do not post usable credentials or other users' data in a public comment. Provide the affected page, minimal reproduction steps and likely impact. Do not access unrelated data or carry out destructive testing.
Content and rights complaints
Provide the exact content URL, an explanation, relevant evidence and a way to reply. For copyright or other rights concerns, explain whether you are the rights holder or an authorized representative. We review the specific content before deciding whether to correct it, restrict public access or remove it. Disagreement or a negative review alone does not establish a violation.
Following up
Public tool reports show their handling status on the report page. Email requests are handled according to their nature; we do not promise an immediate reply or a fixed service deadline. Keep additional details in the original email or report so the context remains together.