did:web:identity.foundation
- Checks
- 3 confirmed · 1 need attention · 3 not confirmed
- Method
- did:web
- Observed
- 2026-11-10 03:27Z
Verdict
Each dimension is evaluated independently. Nothing is averaged.
Verdict
Controlled by the operator of identity.foundation; publishes P-256 verification keys.
- Origin linkage could not be evaluated.
- No verifiable history.
- Organization not established.
Confirmed · 3
- The document is intact and really belongs to this identifier
- It publishes keys that can be used to check signatures
- It was fetched over a valid, secure connection
Needs attention · 1
- No two-way link to a website was confirmed
Not confirmed · 3
- Whoever runs the hosting can change it — no key is needed
- Past versions cannot be proven
- Who is behind it in the real world is not confirmed
| Dimension | State | Evidence |
|---|---|---|
| Document integrity | established | Why Retrieved from identity.foundation and its id equals the DID (SHA-256 ed807e81aac6…).
Reproduce with the APIcurl -s "https://did.is/api/v1/resolve/did%3Aweb%3Aidentity.foundation" | jq '.dimensions[] | select(.id == "integrity")' |
| Key material | established | Why 1 verification method validated (P-256).
Reproduce with the APIcurl -s "https://did.is/api/v1/resolve/did%3Aweb%3Aidentity.foundation" | jq '.dimensions[] | select(.id == "keys")' |
| Update authority | not established | Why not Whoever controls the web server and DNS for identity.foundation can replace this document.
Reproduce with the APIcurl -s "https://did.is/api/v1/resolve/did%3Aweb%3Aidentity.foundation" | jq '.dimensions[] | select(.id == "control")' |
| Origin binding | indeterminate | Why not Linkage proof format not supported: legacy Linked Data proof type 'JsonWebSignature2020' requires JSON-LD/RDF canonicalization, which DID.is does not implement
Reproduce with the APIcurl -s "https://did.is/api/v1/resolve/did%3Aweb%3Aidentity.foundation" | jq '.dimensions[] | select(.id == "origin")' |
| Transport security | established | Why TLS certificate for identity.foundation issued by Google Trust Services, valid until 2026-12-27 (47 days).
Reproduce with the APIcurl -s "https://did.is/api/v1/resolve/did%3Aweb%3Aidentity.foundation" | jq '.dimensions[] | select(.id == "transport")' |
| Verifiable history | not established | Why not did:web keeps no verifiable history; DID.is snapshots are observations, not proofs.
Reproduce with the APIcurl -s "https://did.is/api/v1/resolve/did%3Aweb%3Aidentity.foundation" | jq '.dimensions[] | select(.id == "history")' |
| Real-world identity | not established | Why not Organization not established. DID.is does not verify legal identity or ownership claims.
Reproduce with the APIcurl -s "https://did.is/api/v1/resolve/did%3Aweb%3Aidentity.foundation" | jq '.dimensions[] | select(.id == "organization")' |
Use this result in code
The same request this page made. No account or API key. Expect RESOLVED.
# Nothing to install. No account or API key is needed.
curl -s https://did.is/api/v1/resolve/did%3Aweb%3Aidentity.foundation \
| jq '{outcome: .verdict.outcome, headline: .verdict.headline, checks: [.dimensions[] | {id, state}]}'The verdict is computed by the API, never in this page, so your program sees the same outcome and checks. If you send many requests, honour Retry-After on a 429 response. Quickstart · Rate limits
- DID.is reports evidence; it does not assign trust scores or verify legal identity.
- did:web is as trustworthy as the origin's DNS, hosting and TLS; there is no verifiable history.
- TLS evidence describes the certificate presented to DID.is at resolution time.
- Linked Data proofs that require RDF canonicalization (e.g. Ed25519Signature2020) are reported as unsupported, not valid.
Technical evidence
For developers and auditors. The summary above already reflects everything below.
Evidence graph
Select any plaque to open its forensic detail.
Evidence graph
Current result graph · 2026-11-10 03:27Z
Showing 8 of 8 supplied nodes. All supplied declared items fit within the recorded display limits. A missing node or edge is not proof that a relationship does not exist.
Evidence graph as text
- Inspect relation resolves to from did:web:identity.foundation to DID document, verified, relation subject→document:resolves to, cited evidence /evidence/document/idMatches, /evidence/document/jcsSha256, /evidence/document/jcsProfile
- Inspect relation located at from did:web:identity.foundation to identity.foundation, observed, relation subject→origin:located at, cited evidence /evidence/source
- Inspect relation authenticates from TLS · Google Trust Services to identity.foundation, verified, relation tls→origin:authenticates, cited evidence /evidence/tls
- Inspect relation serves from identity.foundation to DID document, observed, relation origin→document:serves, cited evidence /evidence/source, /evidence/document/jcsSha256, /evidence/document/jcsProfile
- Inspect relation authentication · assertionMethod from DID document to #XXS7zTsbIIAxgNlYEX…, declared, to identifier did:web:identity.foundation#XXS7zTsbIIAxgNlYEXJ4y810GFeLkYdqfK3ChhoQn7c, relation document→key:did:web:identity.foundation#XXS7zTsbIIAxgNlYEXJ4y810GFeLkYdqfK3ChhoQn7c:authentication · assertionMethod, cited evidence /evidence/keys/0, /evidence/document/relationships, /evidence/document/jcsSha256, /evidence/document/jcsProfile
- Inspect relation service from DID document to LinkedVerifiablePresentation, declared, to identifier did:web:identity.foundation#presentation, relation document→svc:did:web:identity.foundation#presentation:service, cited evidence /evidence/services/0, /evidence/document/jcsSha256, /evidence/document/jcsProfile
- Inspect relation service from DID document to LinkedDomains, declared, to identifier did:web:identity.foundation#domain, relation document→svc:did:web:identity.foundation#domain:service, cited evidence /evidence/services/1, /evidence/document/jcsSha256, /evidence/document/jcsProfile
- Inspect relation publishes from identity.foundation to DID configuration, observed, relation origin→linkage:publishes, cited evidence /evidence/domainBinding
- Inspect relation signed from #XXS7zTsbIIAxgNlYEX… to DID configuration, declared, from identifier did:web:identity.foundation#XXS7zTsbIIAxgNlYEXJ4y810GFeLkYdqfK3ChhoQn7c, relation key:did:web:identity.foundation#XXS7zTsbIIAxgNlYEXJ4y810GFeLkYdqfK3ChhoQn7c→linkage:signed:credential:0, cited evidence /evidence/domainBinding/credentials/0, /evidence/keys/0
Bounded projection of evidence for this DID only: at most 40 keys, 40 services, 8 aliases and 8 non-subject controllers. Counts describe this result's evidence, not network completeness, independent corroboration, or all historical relationships. The subject itself is excluded from controller counts. Cycles are allowed; this is not a DAG.
Browse evidence · 8 nodes, 9 relations
Relations in this view
Telemetry
Each stage of the resolution with monotonic timings, as recorded by the resolver.
Telemetry
- DID syntax (DID Core §3.1)syntax.parse0.00 ms
method 'web' · 27 characters
- DID-to-HTTPS transformationmethod.web.transform0.01 ms
did:web:identity.foundation → https://identity.foundation/.well-known/did.json
- DNS resolution and address pinningegress.dns29.1 ms
identity.foundation pinned to 172.67.140.164 (all answers public)
- TLS handshake and HTTP exchangeegress.fetch75.6 ms
GET https://identity.foundation/.well-known/did.json → HTTP 200 · 1367 bytes; leaf certificate identity.foundation issued by Google Trust Services
- JSON parsing and identity checkdocument.parse0.02 ms
1367 bytes parsed; document id equals the requested DID; SHA-256 ed807e81aac6a391
- DNS resolution and address pinningegress.dns1.0 ms
identity.foundation pinned to 104.21.70.240 (all answers public)
- TLS handshake and HTTP exchangeegress.fetch73.8 ms
GET https://identity.foundation/.well-known/did-configuration.json → HTTP 200 · 1135 bytes; leaf certificate identity.foundation issued by Google Trust Services
- Domain linkage credential verification (DIF)linkage.verify0.08 ms
legacy Linked Data proof type 'JsonWebSignature2020' requires JSON-LD/RDF canonicalization, which DID.is does not implement
- Evidence assemblyevidence.assemble0.15 ms
7 dimensions · 8 graph nodes · verdict RESOLVED
Substrate
The raw material behind every statement above.
Substrate
- https://www.w3.org/ns/did/v1DID Core v1.0
- https://w3id.org/security/suites/jws-2020/v1JWS 2020 suite
- https://identity.foundation/.well-known/did-configuration/v1DIF Well Known DID Configuration
- https://identity.foundation/linked-vp/contexts/v1DIF Linked VP
None.
- JCS SHA-256
- 31af489e8f3844fc1b21aea9…
- id equals DID
- yes
Time machine
Observed snapshots and semantic differences between them.
Time machine
Loading observations…
Put it to work
Monitoring and private API access are paid; evidence on this page is never paywalled.
Put it to work
- A
Monitor changes
Get a signed webhook and a 30-day event history when keys, services or the document change. Checked hourly.
Watch this identifier → - B
Resolve from your app
Create a project and an API key. Private resolutions are metered, idempotent and never written to public history.
Create an API key → - C
Read the API
The same request this page made, as a standard W3C resolution or the DID.is evidence response.
Open the API reference →