A URL in, structure out

Point it at a public page and get back the parts you wanted: the readable text without the navigation, the tables as rows, the links, the metadata, the structured data the page already publishes about itself.

It behaves like a guest

The scraper identifies itself honestly rather than pretending to be a browser, honours robots.txt, holds itself to a couple of requests a second per host, and will not touch anything behind a login. Those are not courtesies — a scraper that ignores them gets our outbound address blocked, and that ends the product for everybody using it.

Structure first, text second

Most pages already publish structured data about themselves in JSON-LD, and reading that is more reliable than parsing prose that changes with every redesign. Where it exists it is preferred; where it does not, the tables and the readable text are extracted from the markup instead.

What it will not do

It will not log in, it will not fill forms, and it will not follow links across a whole site on the free lane. A crawler pointed at somebody else's site is a different tool with different obligations, and it is not this one.

Questions

Do you respect robots.txt when scraping?

Yes. The scraper identifies itself honestly, honours robots.txt, holds itself to a couple of requests a second per host, and will not touch anything behind a login. A scraper that ignores those is a scraper that gets our address blocked, which would end the product.

Do you store what I look up?

A lookup is answered and not kept against you. A scan is kept — the account, the target, the time and the authorisation statement — because that record is what an abuse report is answered with, and keeping it is the condition of offering the feature at all.