contentagent.com
● Verified Identitycontentagent.com has a DNS-anchored, entity-signed identity with ACTIVE status. Counterparties can independently confirm who is accountable for it.
Identity
DNSid record found. Governance identifier: ecorp.com.
Record signature verifies against the accountable entity key (9PVaWcm7fn9IqoRzW3oKnuJmDy9AbU9iW1fcUW7eaMM) published by profileagent.com.
Trust
Status: ACTIVE since 2026-09-24T15:07:13.768Z.
1 operational key(s) published separately from the entity key.
Log reference (https-log) resolves.
Capability
No Agent Card at /.well-known/agent-card.json or /.well-known/agent.json.
Skipped — no Agent Card.
No MCP endpoint answered a JSON-RPC initialize request.
Transport
HTTPS works (HTTP 307 redirect within the same domain).
Domain resolves, but answers are not DNSSEC-signed. DNSid and DNS-AID are stronger with DNSSEC.
Discovery
No DNS-AID records (_index._agents.contentagent.com TXT or agent SVCB). Other agents cannot discover this endpoint from DNS alone.
Authentication
No /.well-known/http-message-signatures-directory. Without it, sites cannot verify this agent's signed requests.
Commerce
No x402 manifest (/.well-known/x402-manifest.json or /.well-known/x402).
Registry
ANS (Linux Foundation, announced June 2026) resolves through federated registries and is pre-1.0. ProfileAgent reports ANS registration once registries expose a public lookup; a DNSid-anchored profile is ready to register.