# Tests

On this page, you will be able to check all the tested email addresses and their results.

![](/files/gUHF6inqkEHLJ64DyczJ)

### Action buttons

<figure><img src="/files/aOUkhE78VzqGr9g8waNs" alt=""><figcaption></figcaption></figure>

* **Cancel pending tests:** Clicking this button will remove the email addresses from the testing queue if they have the "Pending" status. You cannot cancel tests for the ones with "In progress" status because they are already being tested by our service.
* **Clear finished tests:** This will delete test results for tests with the "Finished" status.
* **Export:**
  * **Export test results:** This will download a file with all the tests matching the current filters (search and status). Checking rows on the listing prior to clicking the export button has no effect.
  * **Export blocked users:** This will download a file with the email address, date and reason for all the users that have been blocked based on your configuration.
  * **Export deleted users:** This will download a file with the email address, date and reason for all the users that have been deleted based on your configuration.
* **Handle test results:** You can mass block/delete users based on some conditions with this action. You can also select users on the listing before clicking the button to make sure conditions only apply on the selected users.

### Listing

* **Email**: The email address tested
* **Name**: The name of the user that has been tested
* **User status**: It shows if AcyChecker blocked/removed this user based on your configuration. If it did, a red cross will be shown with a tooltip showing the reason
* **Date**: The date when the test has been sent
* **Trustworthiness**: This result isn't taken into account when blocking/deleting fake users. It is calculated based on the results you can see in other columns.
* **Domain exists**: Whether the domain of the email address exists.
* **Disposable**: If the email address is disposable
* **Accept all**: If the domain accepts all incoming emails even if the recipient doesn't exist.
* **Role email**: If the email belongs to a role instead of someone, <support@example.com> is a role based email address.
* **Free**: If the email address was created using a free service, like Gmail for example.
* **Current step:** A test can be **Pending** (either waiting for available credits or for the previous batch to finish), **In progress** (sent to our API and waiting to receive the results), **Finished** (results received), **Failed** (didn't receive the results)
* **Actions**: You can manually unblock/block/delete users with these actions

For the trustworthiness column, here are the possible values:

* **Not existing**: We are sure that this email address doesn't exist, either because the domain doesn't exist or we contacted its domain and it told us that the address didn't exist
* **Risky**: If it is a disposable email address, if we couldn't connect to the domain or if the domain answered with a non-conventional return code
* **Possible**: If the domain exists but refused to answer, or if it's an "accept all" domain
* **Valid**: This is a real email address that is not an accept all domain

### Handle test results

When cleaning your database, you have the option to either automatically block users based on your conditions, or first run a test on the email addresses then decide what to do afterwards.

In the later case, clicking the **Handle test results** button on this page will open this popup:

<figure><img src="/files/bsVfJvNa6HivUdlmZlrM" alt=""><figcaption></figcaption></figure>

You will find the same options as in the [**Clean my database**](/acychecker/clean-my-database.md) menu, and a preview with the number of users matching the selected conditions will be shown at the bottom. Note that users that are already blocked will still count in this preview.


---

# 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.acychecker.com/acychecker/test-listing.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.
