[email protected] — this is the only channel. There is no account system, no support ticket queue and no contact form that stores what you type. Replies usually go out within two working days.
Reporting a wrong result
A hardware verdict depends on the browser that produced it, so a report is only actionable with the surrounding detail. Include the page URL, your browser and its version, the operating system, the device you were testing, and the sentence the tool printed. If a tool shows measured values, copy them as text rather than describing them — the numbers are what identifies the fault.
What this address cannot do
We can explain what a measurement includes and what it leaves out, but we cannot diagnose your specific hardware remotely, authorise a warranty claim, or confirm a fault on your behalf. Every tool runs locally and sends nothing to us, so there is no session, recording or history on our side for anyone to look up. What you send in an email is all we can see.
Privacy of what you send
Email you send is read to answer it and is not added to a mailing list or passed to a third party. Do not attach recordings or camera frames: no tool on this site needs them, and the privacy page explains why none of that material ever leaves your device in the first place.
Suggesting a test
Requests for tools that do not exist yet are welcome, and the ones that get built are the ones a browser can actually measure honestly. If a browser API cannot see the signal you want checked, we would rather say so than ship a number that looks precise and is not. The about page describes where that boundary sits.