Diagnostic tool
Three places declare your encoding. They may not agree.
Paste a URL. Charsetlint reads the character encoding from the HTTP Content-Type header, a byte-order mark, and the <meta charset> tag. It reports which one the browser uses and whether the declarations contradict — including the two mojibake patterns that produce ’ for an apostrophe.
What this tool cannot do
- If the site uses Cloudflare, we cannot reach it — the platform blocks connections to Cloudflare-fronted hosts. This is not a problem with your page.
- The tool reads raw HTML from the server, not the rendered DOM. If your
<meta charset>tag is injected by JavaScript, it will not be detected. - This is a diagnostic tool only — no file conversion, re-encoding, or bulk scanning.
- Only the first ~16 KB of the response body are read. Encoding declarations past that point are not detected.
REPORT A PROBLEM
Found a bug? Have a suggestion?
Your feedback helps improve Charsetlint. Messages go to our team and are read by a human. You can also email charsetlint@agen2ic.ai.