Say what's broken
Bug reports and "why does this tool not do X" are the two most useful messages we get. There is no ticketing system and no chatbot in the way — pick the right address below and it lands in a real inbox.
- Typical reply
- within 2 business days
- General
- [email protected]
- Cost
- free, no account
Who to write to
All of these reach the same team. Using the right one just gets your message read in the right order.
Compose a message
This builds an email and hands it to whatever mail app you already use. Nothing is submitted to us, nothing is stored, and no third-party form service sees it — which is the same answer we give about every tool on the site.
What makes a report useful
A bug report that includes these takes minutes to fix. One that says "the JSON tool doesn't work" usually takes a week of back and forth.
- Which tool, by URL. There are several formatters and they fail differently.
- What you did — pasted, uploaded, clicked which tab.
- What happened versus what you expected.
- Browser and version, and whether it also happens in a private window with extensions off.
- A sample input, if you can share one. Please redact anything real — never send us a live token, key or customer record.
If a JWT, API key or password reproduces a bug, replace the sensitive parts before sending. We do not need the real value, and email is not a safe place to put one.
Security disclosure
If you have found a vulnerability, please report it privately to [email protected] and give us a reasonable window to fix it before publishing. We will confirm receipt, keep you updated, and credit you if you want the credit.
Please do not:
- run automated scanners, load tests or denial-of-service attempts against the site
- access, modify or delete data that is not yours
- use social engineering, phishing or physical attacks against anyone involved
- test third-party services the site depends on — report those to their owners
There is no paid bug bounty at present. That is a resourcing reality, not a judgement on the value of your report.
Before you write
Is a tool down, or is it just you?
Server-side checks (SSL, DNS, headers, SEO) can fail because the target is blocking automated requests, not because our tool is broken. Try a second, unrelated URL first — if that works, the block is at the other end.
Can you audit my site for me?
The tools are self-serve and free; we do not take on consulting work. The SEO Checker and Website Inspector together produce most of what a first-pass audit would tell you.
Do you accept guest posts or link exchanges?
No. Please save us both the email.
Prefer to read first?