One channel, read by a human: hello@nxtolerance.com.

Apache disagrees with the output?

That’s the report that jumps the queue. If your server rejects or misbehaves on a generated rule, send four things:

1. the exact block you pasted (copy it out of the output panel),
2. what Apache did — the error-log line, the 500, the wrong Location: header,
3. your Apache version (apachectl -v) and the relevant modules (apachectl -M),
4. your host type — shared cPanel, your own VPS, behind Cloudflare/a proxy.

“Right” sometimes means “right on 2.4 with mod_expires loaded.” Version and module list are what turn a report into a fix.

Feature requests

Describe the rule you’re after and the server context — “I need to redirect only when a query param exists” beats “add more redirects.” Genuinely useful candidates get added to the form; Apache 2.4 coverage is the boundary (no Nginx, no IIS web.config — different grammars, different tools).

Wrong claim in a guide?

Quote the line, give the correct behavior and the Apache version it applies to, and include the page URL — e.g. 301 redirects, mod_rewrite basics, password protection.

Everything else

Broken rendering, accessibility issues, press or partnership — same address, and include the URL if it’s about a specific page.

Response expectations

No ticket system, no autoresponder. A reproducible report like “Require not ip emitted outside RequireAll” gets an answer within days; vaguer notes take longer but all are read.