foundrynet.com valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Claim my listing on Agent Web Map for foundrynet.com:
1. POST https://agentwebmap.com/v1/sites/foundrynet.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://foundrynet.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/foundrynet.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/foundrynet.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

FoundryNet

Vendor-neutral guides to load balancing, switching, routing and monitoring, plus an independent archive of the Foundry Networks product lines and CLI.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T00:43:20.765Z. Cached copy · Source on foundrynet.com

# FoundryNet

> Vendor-neutral guides to load balancing, switching, routing and monitoring, plus an independent archive of the Foundry Networks product lines and CLI.

An independent network engineering reference and the unofficial archive of Foundry Networks (1996 to 2008). Guides explain load balancing, Ethernet switching, routing and network monitoring in vendor-neutral terms, with IronWare configuration shapes as worked examples, and a growing set of pages on AI crawler, bot and agent traffic at the edge. One named editor; every guide links its standards and sources. No advertising, no cookies, no cross-site tracking. Not affiliated with Foundry Networks or its successors.

## Newest: provenance on the wire (authenticity at the network layer)
- [Bot Verification: Proving a Crawler Is Who It Claims to Be](https://foundrynet.com/provenance/bot-verification/): How to verify the origin of a client claiming to be a search or AI crawler: reverse then forward DNS, published IP range feeds, RFC 9421 signatures, a log.
- [mTLS Between Edge and Origin: Mutual TLS as Proof of Both Ends](https://foundrynet.com/provenance/mtls-edge-to-origin/): Mutual TLS proves both ends of an edge-to-origin connection, provenance for the link itself: the TLS 1.3 client certificate exchange, a private CA, rotation.
- [Content Integrity in Transit: Proving a Response Arrived Unchanged](https://foundrynet.com/provenance/content-integrity-in-transit/): How to prove a response arrived unchanged and verify the source: where TLS stops, Subresource Integrity, RFC 9530 Content-Digest and Repr-Digest, signatures.
- [Edge Logs as Evidence: An Audit Log That Proves What Was Served](https://foundrynet.com/provenance/edge-logs-as-evidence/): How to keep edge and balancer logs with a chain of custody: fields that prove what was served, NTP time, RFC 5424 syslog, RFC 5848 signatures, retention.
- [RPKI and Route Origin Validation: Proving a Route Is Authentic](https://foundrynet.com/provenance/rpki-route-origin-validation/): How RPKI lets a router verify the origin of a BGP route: what an ROA states, how validators build VRPs and feed routers over RTR, the three validation states.
- [C2PA Through a CDN: Serving Content Credentials Without Breaking Them](https://foundrynet.com/provenance/c2pa-through-a-cdn/): Serving files that carry a C2PA manifest through a CDN, optimiser or proxy: where the manifest lives, what breaks the signature, pass-through and testing.
- [Image Metadata Through the Pipeline: What Survives Optimisation](https://foundrynet.com/provenance/image-metadata-through-the-pipeline/): Which image metadata blocks (EXIF, IPTC, XMP, ICC, C2PA) exist in JPEG, PNG, WebP and AVIF, which operations strip them, and how to inspect and preserve them.
- [Syslog as Evidence: Provenance and Integrity of Network Logs](https://foundrynet.com/provenance/syslog-as-evidence/): Syslog per RFC 5424, RFC 3164 and RFC 5425 TLS, why provenance and integrity decide whether a log is evidence, and
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=foundrynet.com · GET /v1/domain/foundrynet.com · this page as Accept: application/json or text/markdown · MCP lookup_domain