Last Updated:

Domino Anonymizer — a small tool for a recurring problem

HCL Domino

 

Before sending NSD files, crash dumps, or server logs to HCL support or a consultant, you need to strip out sensitive data. Server names, user Distinguished Names, IP addresses, file paths — they're all in there.

I built a standalone HTML tool that handles this client-side. Nothing is uploaded anywhere. You drop the files, choose which patterns to redact, and download the cleaned versions.

Supported formats: .log .dmp .nbf .out .csv .pml

Replacements are consistent — the same original value always maps to the same token across all files in a batch. The tool also exports an anonymization map as CSV, which you can share under NDA with the support team if they need to reverse a specific entry.

No framework, no dependencies, no install. One HTML file.

----------------------------

What it anonymizes:

PatternExample → Result
Notes DNCN=John Smith/OU=Finance/O=AcmeCN=USER_001/OU=DEPT_001/O=ORG_001
IPv4192.168.1.5010.0.0.1
IPv6fe80::1fd00::001
Emailsjsmith@acme.comuser001@anon.example
FQDNsdomino1.acme.comserver-001.example.com
Windows pathsC:\Users\jsmith\C:\Users\WINUSR001\
Unix paths/home/jsmith//home/unixuser001/
MAC addresses00:1A:2B:3C:4D:5E → anonymized
GUIDs/Replica IDs32-hex UNIDs, UUID format
License/Serial keysalphanum groups with -

Key features:

  • Consistent mapping — same original value always gets the same token across all files in a batch
  • Binary files (.dmp, .nbf) — handled via latin-1 byte-safe round-trip, ASCII strings replaced in place
  • Anonymization map downloadable as CSV — so HCL/IBM support can reverse specific values under NDA
  • Checkboxes to enable/disable each rule category
  • "anon_" prefix on output filenames so originals are never overwritten

Contact_ dperarnaud [@] data101.es