Support chat

The dataset below contains 30 fictional support messages with ordinary text, contact details, or API tokens. Below, we’ve run Email addresses and API token formats checks on it to check support logs for contact details and API tokens.

Text

Results

Records checked
30/30
Records flagged
15/30 (50%)

Actions

Categories

Checks

Records

Quick filters:
Text CategoriesActivate to sort ascending. ChecksActivate to sort ascending. DecisionActivate to sort ascending. ActionActivate to sort ascending.
The pasted debug line says api_token = ghp_1234567890abcdefghijklmnopqrstuv Secrets API token formats Review Redact and review
Rotate the fictional token ghp_abcdefghijklmnopqrstuvwxyz1234567890 Secrets API token formats Review Redact and review
The test ticket includes api_key = sk-fictional1234567890abcdefghij Secrets API token formats Review Redact and review
Remove api_token = ghp_trainingonly0123456789abcdefghijkl from the chat export Secrets API token formats Review Redact and review
The customer pasted api_key = sk-exampleonly0987654321abcdefghij Secrets API token formats Review Redact and review
A diagnostic reply contains api_token = ghp_demo9876543210abcdefghijklmnopqrst Secrets API token formats Review Redact and review
The sample attachment repeats api_key = sk-placeholder1234567890abcdefghij Secrets API token formats Review Redact and review

Use this with your own content

Configure similar checks for your own dataset or product

Set up your own checks