Web Clients

When receiving a request from us, there are a couple ways you can verify it as a legitimate request.

Agents

We utilize different client identifiers (or agents) based on our purpose for accessing web services. For standard HTTP requests, the agent can be found in the standard User-Agent header.

Namedgraph-Fetch

The Namedgraph-Fetch agent is used for retrieval of remote content from traditional websites. This includes the Inspector and Web Data API services. The User-Agent will look similar to the following (and may include additional browser- or client-specific details).

This agent respects access directives (such as robots.txt) that match Namedgraph-Fetch.

Namedgraph-Rpc

The Namedgraph-Rpc-* agent is used for direct connections with external service providers and is typically based on an established API with additional authentication properties. These agents support customer-managed requests for data synchronization. The User-Agent will look similar to the following (and may include additional client-specific details).

Namedgraph-Verify

The Namedgraph-Verify agent is used for accounts that choose to verify ownership of domain or web properties. Requests are performed periodically to maintain a verified status, and are automatically stopped after repeated failures.

Network

All client requests originate from IP addresses which can be verified through DNS. A reverse DNS lookup will return a subdomain of client.namedgraph.net, and the host will have a reciprocal A record.

These IP addresses may change over time, and a successful DNS verification may be cached for up to 28 days.

Verification Example

The following steps demonstrate verification using the host command and example IP address.