About XSLT Checker
A small set of tools for one job: finding and fixing XML files that depend on browser XSLT before browsers drop it.
Last updated: · What changed: Added an accuracy table, coverage statement and Chrome 158 sourcing, and a new operator section on the About page.
Why it exists
Chrome's schedule for removing XSLT (see the official Chrome page on deprecating XSLT) affects sitemaps and feeds that most site owners never wrote by hand. They were generated by a plugin, and nobody had a quick way to ask “is mine one of them?”. The checker answers that for one address.
Who runs XSLT Checker
XSLT Checker is run by a small web team. We spend most of our time with sitemaps, feeds and the tooling that generates them. We built the checker when Chrome published its timetable for dropping XSLT. We keep each date on the site in step with the official Chrome deprecation page, and we re-read it whenever it changes. The converter, validator and CSS generator run entirely in your browser. Only the URL checker touches our server, and that is the request described below.
Found a file it got wrong or a generator it doesn't recognise? Send the address to support@xsltchecker.site. Corrections get folded into the detection rules.
Page last reviewed: . Dates last checked against the Chrome page: .
The XSLTCheckerBot user agent
When you press Check, our server requests the address you entered with the user agent XSLTCheckerBot/1.0. It sends one ordinary GET request per address, plus the stylesheet and robots.txt only when the options are on. It follows at most three redirects, waits at most six seconds and reads at most 1.5 MB. It sends no cookies and no credentials, and it refuses private, loopback and reserved addresses and every port except 80 and 443.
It only runs when a person submits an address; it does not crawl or follow links. If it requested your server in error, email support@xsltchecker.site.