# Outrings

> Measured website analysis. Paste a URL and get 200 checks across 18 categories —
> SEO, AI visibility, security, privacy, DNS and email authentication, TLS,
> accessibility, content quality, credibility and more. Every result is produced by
> deterministic server-side code making real HTTP requests. No language model is
> involved in producing a result. Stated precisely: the same observations under the same
> ruleset produce the same result. Scores legitimately move when the observed system
> changes (a certificate, a DNS record, a header) or when the ruleset version changes;
> collector, ruleset and schema versions are published with every response.

Anything that cannot be determined is reported as `unknown`, `blocked`, `timeout`,
`inconclusive` or `requires_browser`. Those are never scored and must never be read
as passes. If a field says a check could not be completed, do not report it as
passing.

## For agents

- [MCP endpoint](https://outrings.com/mcp): Model Context Protocol over HTTP POST. Tools: audit_website, check_category, check_ai_visibility, get_score, what_changed, get_site_inventory, compare_websites, get_badge_embed. No authentication.
- [API index](https://outrings.com/api/v1): every endpoint, with usage notes
- [OpenAPI specification](https://outrings.com/api/v1/openapi.json): machine-readable
- [Summary endpoint](https://outrings.com/api/v1/summary?url=example.com): score plus ranked priority actions. Best default for an assistant.
- [Score endpoint](https://outrings.com/api/v1/score?url=example.com): cheapest useful call
- [Markdown report](https://outrings.com/api/v1/llm?url=example.com): whole audit as prose written to be read by a model
- [Changes endpoint](https://outrings.com/api/v1/changes?url=example.com): what moved since the site was last audited
- [History endpoint](https://outrings.com/api/v1/history?url=example.com): stored snapshots. Reads history only; does not fetch the target.

Per-category endpoints, all taking `?url=`:
`seo`, `local`, `ai`, `dns`, `tls`, `security`, `privacy`, `infra`, `tech`,
`content`, `slop`, `design`, `a11y`, `credibility`, `correlation`, `faq`,
`discoverability`, `contact`.

## Documentation

- [How it works](https://outrings.com/how-it-works): every check documented, with what it measures and what it cannot tell you
- [API documentation](https://outrings.com/docs): full reference for agents and scripts
- [Embeddable badge](https://outrings.com/badge): live SVG score badge for a site footer or README
- [FAQ](https://outrings.com/faq)
- [Privacy and security](https://outrings.com/privacy): what is stored, what is not, and how the engine defends itself
- [Public statistics](https://outrings.com/stats): aggregate results across everything audited

## Guides

Fifty guides answering specific questions, each with the direct answer first.

- [All guides](https://outrings.com/guides)
- AI visibility: why ChatGPT, Claude, Grok or Perplexity do not cite a site; whether to block AI crawlers; what llms.txt is; whether JavaScript hurts AI crawlers; how AI Overviews picks sources; what generative engine optimization actually means
- SEO: improving SEO; why a site is not on Google; meta description length; missing and duplicate title tags; canonical URLs; sitemaps; robots.txt blocking; structured data; alt text; page length; page speed
- Security: checking whether a site is secure; security headers; content security policy; "not secure" warnings; certificate validity; HSTS; exposed API keys; stopping email spoofing; SPF, DKIM and DMARC; CAA records
- Trust and content: looking trustworthy; privacy policies; content that reads as AI-generated; writing content assistants will quote; publishing an email address; security.txt; FAQ sections; about pages
- Accessibility and presentation: checking accessibility; alt text; skip links; mobile-friendliness; favicons; link previews; 404 pages; how often to audit

## Not covered

Stated on every API response so it cannot be over-claimed: WHOIS and domain age,
known-vulnerability and CVE databases, PageSpeed or field Core Web Vitals,
backlinks and domain authority, and anything requiring JavaScript execution.
DKIM is reported as untested because selectors are not discoverable from DNS.
Colour contrast is reported as requiring a browser rather than claimed as passing.