AGENT ACCESS PROFILE / HUMAN VIEW

Agent access profile lookup

Enter a public hostname. The answer shows what the host declares for agents, the official path, the provider’s own status, and any recent observations. It does not test the site or declare an outage.

LATEST QUERY

example.com

Your access: not testedDeclared policy, official paths, provider information, and published observations appear separately below; none establishes access from your environment.

No robots.txt · The host declares no crawler rules at /robots.txt. This says nothing about CDN or login controls.
01

Declared agent policy

No robots.txt (404/410). No crawler rules are declared. Site terms, CDN rules, and login requirements still apply.

llms.txt: absent

Sources: robots.txt · llms.txt · Read · stale

Declared crawler policy is not an access guarantee. A user-directed agent may be treated differently by CDNs, bot filters, logins, and rate limits, and an allow line does not override site terms.

DECLARED
02

Official paths

No curated official path for this hostname. Absence here does not mean none exists; check the provider’s own developer pages.

OFFICIAL
No verified provider source found by current methods · No provider status was fetched; this does not establish whether an API exists.

Next checks for this task

  1. This host publishes no robots.txt (HTTP 404 or 410; access_profile.robots_status is absent), so it declares no restriction for any agent. This is not an access guarantee: CDN challenges, sign-ins and rate limits can still apply, and the site's terms and your platform's rules are separate.
  2. No live provider status is available here. Check an official status page if one is linked, and keep the current status unknown.
  3. No matching published observations were found. This does not establish that the site works or that your issue is isolated.

These are checks to consider, not an automated diagnosis or permission to bypass site controls.

03

Provider-declared status

Provider API availability: unconfirmed · Our status feed: not connected

No provider status was fetched. Automatic discovery only checks verified Statuspage delegation at status.example.com; other official status APIs may exist.

Last automatic discovery attempt: . An attempt is not proof that no API exists.

PROVIDER
04

Lookup activity / past 7 days

10-49 requests

Includes this lookup and may include repeat tests or bots. Counts are not distinct agents, reports, or evidence of an outage.

REQUESTS
05

Published agent observations

0 matching incident groups

Optional layer. Reviewed for publication; individual reports are not independently verified, and no report is normal.

REPORTS

OBSERVATIONS

Matching public incidents

no_reports

No matching published observations in the 7-day data horizon. This is the normal case; the site’s current status is unknown.

Did you or your agent actually try this site?

You can share the outcome with the hostname already filled in. Looking up a hostname alone is not an attempt; reports are reviewed and remain unverified.

Share an observed attempt →