> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/enterprise-portal/verification-logs/secure-sna.md).

# Secure SNA logs

The Secure SNA logs view lists every Secure SNA check made by your project, newest first. Click any row to drill into a specific check.

For background on what Secure SNA is and how the verification flow works, see the [Secure SNA product page](/products/number-verification/secure-sna.md).

## What you see in the list

Each row represents a single check. The columns typically include:

| Column              | What it shows                                                                             |
| ------------------- | ----------------------------------------------------------------------------------------- |
| **Check ID**        | The `check_id` returned at creation. Use this to correlate with logs in your own backend. |
| **Date/Time (UTC)** | When the check most recently transitioned state.                                          |
| **Status**          | `COMPLETED`, `EXPIRED`, `ERROR`.                                                          |
| **Match**           | `true` / `false` — the verification result, present only when `status` is `COMPLETED`.    |
| **Network**         | Mobile network operator (MNO)                                                             |

Clicking a row opens the check's detail view, including an  **`error_code`** if the check ended in `ERROR` or `EXPIRED`. See [Secure SNA error codes](/products/number-verification/secure-sna/error-codes.md) for what each `error_code` means.

## Filters

* **Search by phone number** — finds every Secure SNA check for a specific MSISDN. Useful when investigating a user-reported issue.
* **Filter by status** — narrow to `COMPLETED`, `EXPIRED`, `ERROR`.
* **Filter by date range.**
* **Filter by network**

## Retention

Production checks are retained for the period specified in your IDlayr Trust Center attestations — see [Compliance & Security](https://gitlab.com/4auth/product-documentation/-/blob/main/help/compliance-and-security.md). Sandbox `EXPIRED` and `ERROR` checks are **not persisted** and won't appear in this view.

## What's next

* [**Secure SNA product page**](/products/number-verification/secure-sna.md) — background on the verification flow.
* [**Secure SNA error codes**](/products/number-verification/secure-sna/error-codes.md) — what each terminal-state and HTTP error means.
* [**Verification logs hub**](/enterprise-portal/verification-logs.md) — links to logs for the other products.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.idlayr.com/enterprise-portal/verification-logs/secure-sna.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.