Make anything safe to paste into a ticket
A customer sent you a log, a HAR capture, or a raw error dump. Before it goes into a ticket, a vendor thread, or a bug report, clean it here — redact PII, strip secrets, and sanitize captures locally, so nothing sensitive ever leaves your machine.
Run the Log Sanitizer workflow → Sanitize a HAR file →
Launch a tool
Tip: press 1–8 to open one- 1HAR SanitizerRedact secrets with custom rules, and export Postman / cURL / fetch packs.
- 2PII DetectorFind and redact personally identifiable information.
- 3Secrets ScannerDetect API keys, tokens, and credentials in payloads.
- 4HTTP HeadersParse / edit headers in a grid, detect duplicates.
- 5Timestamp ConverterUnix epoch ↔ local / UTC / ISO with shareable links.
- 6JSONL Log ViewerInspect newline-delimited JSON logs with field filters.
- 7Timezone & Date MathConvert times across timezones, add/subtract durations.
- 8JSON FormatterValidate, pretty-print, minify with tree view and secret detection.
Run a workflow right here
Runs locally — nothing is uploadedLog Sanitizer (PII + secrets)
Redact PII (emails, phones, cards) and then scan the redacted text for likely secrets. Best-effort local checks.
pii-detector-redactor → secrets-scanner 2 steps · Runs automaticallySnippet Redact, Scan & HAR Handoff
Paste a request/response snippet to redact PII and flag secrets, then hand off to the HAR Sanitizer for whole-HAR-file cleanup.
pii-detector-redactor → secrets-scanner → har-sanitizer 3 steps · 2 automatic · 1 needs your reviewBase64 Payload Secret Scan
Base64-decode an opaque payload and scan the decoded text for secrets and tokens.
base64-tool → secrets-scanner 2 steps · Runs automaticallyTrack a checklist
Progress is saved on this deviceDaily tasks, guides & FAQ
Common daily tasks
- Redact emails, phone numbers and card numbers from a customer log
- Strip cookies, tokens and Authorization headers from a HAR capture
- Scan a pasted error dump for API keys and secrets before escalating
- Parse a raw HTTP response header block to explain a failing request
- Convert a Unix timestamp from a log into a readable date
- Line up event times across timezones when reconstructing an incident
Recommended workflows
- Log Sanitizer — redact PII, then scan the log for leftover secrets.
- HAR Redact Prep — redact and scan a capture, then hand off to the HAR Sanitizer.
- Base64 Decode Secret Scan — decode a Base64 blob a customer pasted and check it for secrets.
Top tools
HAR Sanitizer
Strip cookies, tokens and Authorization headers from a HAR file before you attach it to a ticket.
Sanitize a HAR file →PII Detector & Redactor
Find and mask emails, phone numbers, IPs and card numbers in a pasted log or transcript.
Redact PII →Secrets Scanner
Catch API keys, tokens and passwords hiding in a dump before it leaves your team.
Scan for secrets →HTTP Headers Parser
Parse a raw request/response header block to explain what actually happened.
Parse headers →See the full security & debugging tool cluster →
Why browser-local matters for support engineers
Support work means handling whatever a customer pasted — logs, HAR captures, tokens, and personal data you never asked for. Tool input is processed in this browser and is not sent by DDT tools. DDT runs no browser analytics scripts, sets no tracking cookies, and collects no browser product events. The CDN handles ordinary page requests and provides aggregate traffic counts. That means you can clean an artifact for a ticket or a vendor without forwarding a customer's secrets to a third-party service.
FAQ
Is the customer data I paste uploaded anywhere?
No. Tool input is processed in this browser and is not sent by DDT tools. DDT runs no browser analytics scripts, sets no tracking cookies, and collects no browser product events. The CDN handles ordinary page requests and provides aggregate traffic counts. Logs, HAR files and personal data are cleaned in memory and never sent to a server.
How do I make a HAR file safe to attach to a ticket?
Run the HAR Sanitizer: it redacts cookies, Authorization headers, tokens and request bodies locally so the capture is safe to share with a vendor or attach to a bug.
How do I remove personal data from a customer log?
Use the PII Detector & Redactor to mask emails, phone numbers, IP addresses and card numbers, or run the Log Sanitizer workflow to redact PII and scan for secrets in one pass.
A customer pasted a token in the chat - how do I check what it is safely?
Paste it into the Secrets Scanner to confirm whether it is a live credential, or the JWT Decoder to read its claims - both run locally, so nothing is transmitted.
Related
- Security engineers — scan secrets, sanitize logs, verify signatures.
- API developers — decode tokens, verify webhooks, debug responses.
- HAR sanitization checklist — a step-by-step pre-share review.
- Sanitize a HAR file before sharing it with support