Editorial policy
One question, answered first
Each page answers one question in its opening paragraph, then shows the example, table or steps behind the answer. Every page ends with what it does not cover and its sources.
Evidence, not verdicts
We never call a URL safe, and we do not turn a report, a missing warning or a clean structural check into a verdict. A report is described as a dated observation by a named source about a stated subject. No match, a failed check, unknown coverage and old evidence are kept apart.
Source, result, observation, inference
Every page keeps four kinds of statement apart: what a standard, provider or document states, what a parser or calculation produced from stated inputs, what we observed in a named browser or runtime, and what we infer. Anything we did not run stays “not tested”.
Provider policies are recorded with dates
What a service says about submitted URLs is taken from its own terms, privacy notice or documentation, with the date checked and the type of source labelled. A field the source does not address is recorded as unknown, which does not mean no retention, no sharing or no private option. We do not submit test URLs to providers.
No help evading warnings or filters
We explain how to read warnings and where to request a review. We do not publish ways to bypass browser warnings, mail filters or blocklists.
Your input stays with you
Our tools process addresses in your browser, show them as text rather than links, and make no network request with what you enter. Each tool page says how this was checked and what the check does not cover.
Original work only
Explanations, examples, fixtures and compilations are written new for this site. We do not reuse prose, code, images, reports or data from earlier sites or services at this domain.
AI assistance and responsibility
Pages are drafted with AI assistance. The publisher is responsible for every page: claims are checked against their sources and tests before publication, and errors are corrected in public as described in corrections.
Review
Independent review by a named security engineer is being added. A reviewed page shows the reviewer’s name, credential and review date. Reviewers must be independent of any sponsor on the page.
Sponsors
No sponsor may determine an answer, comparison row, directory entry, inclusion or ordering. Sponsor modules never appear on the URL inspector, the datasets, the policy comparison or the reporting-route directory, or on any page that compares or lists products in the sponsor’s category. See disclosure.