Contact

There is no contact form here. A form would mean a server endpoint, and a server endpoint is the thing this site does not have. Email is also easier to reply to.

Reporting a bug in a tool

The useful bug report is a document that reproduces it. Include the smallest XML that shows the problem, say what you expected and what happened, and name your browser.

Please redact anything sensitive before sending. This site is built so that your documents never reach us, and an email is not covered by that: once you send it, we have it. Reduce it to the smallest fragment that still fails.

Correcting an article

The guides make specific claims about specifications and about how particular parsers behave. Some of them will be wrong. If you find one, say which page, which sentence, and what the correct position is. A pointer to the relevant clause or to the implementation source is more useful than an assertion, and it gets fixed faster.

Suggesting a tool

Worth saying: what you were trying to do, what you used instead, and what was wrong with it. The most useful suggestions describe a task rather than a feature.

Security

If you have found a way to get script execution out of a document pasted into one of these tools, or any other security issue, please report it privately to the address above before disclosing it. It will be treated as urgent.

What this address is not for

Link exchanges, guest posts, sponsored content and directory submissions all go straight to the bin. Nothing on this site is for sale.