# Alias Token Queries

Use alias tokens to verify account status and compliance signals without handling personal identity data. JSON is the preferred interface for application integrations; DNS TXT lookups are available for resolver-based workflows.

### What this is for

Query non-personal account and compliance signals for a Yoursafe YOU account using an alias token.

### Recommended path

Use JSON queries for application integrations. Use DNS TXT queries for resolver-based environments.

### Core checks

Check `accountstatus`, screening timestamps, and serial values to detect meaningful updates.

## Ways to query

### JSON

One HTTPS call returns account status and screening fields. Use this in an application.

[Open JSON queries](/en/alias-token-json)

### DNS

Look up a single field from a DNS TXT record when a resolver fits the environment better than HTTPS.

[Open DNS queries](/en/alias-token-dns)

## Operational best practices

- Poll at intervals aligned with your compliance posture (on login, payout, or scheduled checks).

- Persist latest values and compare new results to detect status transitions quickly.

- Alert or pause sensitive flows when `accountstatus` is inactive or screening data is stale.

- Log query outcomes for auditability, while minimizing retention of unnecessary metadata.

Next: [JSON queries](/en/alias-token-json)

Read account status and screening fields with one HTTPS call.