# DNS queries

##### Request

                      dig TXT accountstatus.<aliastoken>.yoursafe.id

Looks up a single field value from DNS TXT records.

##### Response

### Example TXT answer

                      accountstatus.xyz123.yoursafe.id. 300 IN TXT "active"

**DNS TXT reliability**

DNS responses are cache-sensitive. Design for TTL propagation and normalize TXT parsing across environments.

### TXT record structure

                  <>

- `Name`: `..yoursafe.id`

                  <>

- `TTL`: Cache duration in seconds as returned by DNS.

                  <>

- `TXT value`: The field value, for example `"active"`.

### Common fields

                <>
                  aliasserial
                  accountstatus
                  country
                  countrycode

                <>
                  eighteenplus
                  idverifieddate
                  peplistdate
                  sanctiondate

                <>
                  uksanctionlists
                  unsanctionlists
                  ussanctionlists
                  eusanctionlists

                ibanserials

### DNS checklist

- Design for resolver caching and TTL delays before updates become visible.

- Normalize TXT parsing because quoting/formatting can vary by tooling.

- Use DNS when it matches your infrastructure; prefer JSON for richer app integration.

Next: [Endpoint Reference](/en/id-oidc-endpoints)

Look up OIDC endpoints for discovery, tokens, userinfo, and logout.