# Domain names and Certificates

## Domain names

Suggested convention:

\<component>.\<environment>.\<your org domain>.\<tld>

<table><thead><tr><th width="282">Component</th><th width="417">Example Domain</th></tr></thead><tbody><tr><td>Social Registry</td><td>socialregistry.dev.openg2p.org</td></tr><tr><td>Logging dashboard</td><td>opensearch-sr.dev.openg2p.org</td></tr><tr><td>Reporting dashboard</td><td>opensearch-sr.dev.openg2p.org</td></tr><tr><td>Minio console</td><td>minio-sr.dev.openg2p.org</td></tr><tr><td>ODK Central</td><td>odk-sr.dev.openg2p.org</td></tr><tr><td>eSignet</td><td>esignet-sr.dev.openg2p.org</td></tr><tr><td>Apache Superset</td><td>superset-sr.dev.openg2p.org</td></tr><tr><td>Kafka dashboard</td><td>kafka-sr.dev.openg2p.org</td></tr></tbody></table>

All the above domains point to Nginx IP corresponding to server (virtual host) that routes to Istio Ingress gateway server on OpenG2P Cluster.

## Certificates

SSL certificates for all the above must be available, generally as a wild card certificate for the domain, example. `*.dev.openg2p.org`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.openg2p.org/operations/deployment/_archive/domain-names-and-certificates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.