rdfreader

Paste any IRI. We dereference it the way a linked data client should, parse whatever comes back, and render it as a page a person can actually read.

No account, no upload, nothing stored. Each request fetches and parses live at the edge.

Try these

Archdiocese of Los Angeles Textbook content negotiation: a 303 redirect for browsers, Turtle and JSON-LD for clients.
The FOAF vocabulary A classic ontology. Renders as a class and property listing rather than a resource page.
DBpedia: Los Angeles Large instance record. Labels get resolved so the page reads as prose, not identifiers.
Wikidata: Q42 Opaque identifiers, deep redirect chain. The chain is shown rather than hidden.

Reads the real web, not just the semantic web

When a server ignores your Accept header and hands back HTML, we mine it for embedded JSON-LD instead of giving up. That is where most structured data actually lives.

Every page is also an API

Swap /r for /api/resolve and the same pipeline returns JSON, with the redirect chain, the resolved subject, and any parse warnings.

Permalinks, server rendered

A resolved IRI is a URL you can cite in a paper or paste into a ticket, it works with JavaScript off, and link previews resolve. Client-only viewers cannot do any of that.

Honest about what it dropped

Unresolvable terms, unsupported serializations, and subject mismatches are reported on the page rather than quietly discarded.