Skip to main content
Bot Information

Aho DomainHealth Bot

Automated monitoring service that ensures verifiable credential infrastructure remains operational and accessible.

What does it check?

DID Configurations

/.well-known/did-configuration.json

Checks the availability of your DID Configuration document for domain linkage verification.

Learn more

DID Documents

/.well-known/did.json

Verifies that your Decentralized Identifier document is properly formatted and accessible for DID resolution.

Learn more

OpenID4VCI Metadata

/.well-known/openid-credential-issuer

Monitors your OpenID for Verifiable Credential Issuance metadata endpoint.

Learn more

JSON-LD Contexts

JSON-LD context document defining credential vocabulary and term mappings.

Learn more

JSON Schemas

JSON Schema document for validating credential structure.

Learn more

Web Pages

Validates that your website's main pages are accessible and returning proper HTTP responses.

Vocabulary Terms

Vocabulary document defining semantic terms for credential claims.

Vocabulary Term (HTML)s

HTML vocabulary document with human-readable term definitions.

Vocabulary Term (JSON-LD)s

/vocab.jsonld

JSON-LD vocabulary document defining semantic terms.

Learn more

Vocabulary Term (RDF/XML)s

/vocab.rdf

RDF/XML vocabulary document defining semantic terms.

Learn more

Vocabulary Term (Turtle)s

/vocab.ttl

RDF Turtle vocabulary document defining semantic terms.

Learn more

How often does it check?

Check frequency depends on the endpoint type and its current health status.

Endpoint Type Check Interval
DID Configurations 1 day
DID Documents 1 day
OpenID4VCI Metadata 1 day
JSON-LD Contexts 7 days
JSON Schemas 7 days
Web Pages 7 days
Vocabulary Terms 7 days
Vocabulary Term (HTML)s 7 days
Vocabulary Term (JSON-LD)s 7 days
Vocabulary Term (RDF/XML)s 7 days
Vocabulary Term (Turtle)s 7 days

Degraded Endpoints

Checked more frequently to detect recovery as quickly as possible.

Unreachable Endpoints

Use exponential backoff (up to 7 days) to reduce load on your servers.

How to identify this bot

The DomainHealth bot identifies itself with the following User-Agent string:

User-Agent 
Aho-DomainHealth/1.0 (+https://aho.com/about/bots/domain-health)
Bot name
Aho-DomainHealth
Version
1.0
Timeout
10s
Max redirects
5

Why is this bot checking my domain?

Your domain is being monitored because it is associated with verifiable credential issuance or verification on the Aho platform.

  • Ensure credential verification can successfully resolve your DID
  • Alert administrators to endpoint outages or misconfigurations
  • Maintain trust in the verifiable credential ecosystem

Robots.txt compliance

The DomainHealth bot respects robots.txt directives for general web page checks.

However, it will still check well-known protocol endpoints (/.well-known/*) as these are required for verifiable credential infrastructure to function.

Questions or concerns?

If you have questions about our monitoring, wish to adjust the check frequency, or want to request removal of your domain from monitoring, we're here to help.

Please include:

  • The domain(s) in question
  • Your relationship to the domain (owner, administrator, etc.)
  • The specific concern or request
Contact Us