dns.records

DNS and registry — records. Give it name, types.

What it takes

dns.records takes name, types. The domain to look up, e.g. example.com. Required by resolve/records/rdap.

What it gives back

The answer is the provider's own structure, passed through rather than reshaped, so nothing is lost between the resolver and you.

The same verb everywhere

Running this from the page, posting dns.records to /api/netinfo/run, and giving it to a coding agent over MCP are three doors onto one implementation. There is no separate website version that behaves differently from the documented one, which is the whole reason the verb has the same name in all three places.

Questions

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.

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.