Reading results

Every check in the iw Toolbox presents its result the same way. Once you know the layout, you can read any report at a glance.

The header

Above the result is what was checked, for example inwendo.de A or inwendo.de. In front of it sits a large status dot in the colour of the worst finding. On the right, small dots count how many findings there are per level. At the far right is the export icon.

The four levels

Colour	Level	Meaning
Green	In Ordnung (OK)	Checked and correct. Nothing to do.
Blue	Hinweis (note)	For information, such as the response time, a CNAME chain or the next signature expiry. Not an error.
Yellow	Warnung (warning)	Works, but is risky or unusual. Worth a look.
Red	Fehler (error)	Something is broken or missing, with noticeable effects on reachability or delivery.

Hover over a dot to see the name of its level. Findings are sorted by severity, errors first. Each finding has a bold statement and, where needed, a line below that explains the cause and what to do.

A blue overall dot doesn’t mean “bad”. It only means there’s something to know, but nothing to fix.

The tabs

Below the header you switch between three views. The number in brackets shows how many entries each contains.

Ergebnis (result)

First the findings, then the check’s tables, such as Antwort (answer) for DNS Lookup, Vertrauenskette (chain of trust) for the DNSSEC check or Nameserver for the name server check. Empty cells show a dash. Each table has an Als Text kopieren (copy as text) icon at its top right. It copies the table tab-separated, so you can paste it straight into a spreadsheet or a ticket.

Rohdaten (raw data)

Every DNS response the check received, in dig format. Above each block are the command, the protocol (UDP, TCP or DoH) and the response time. Checks that do more than DNS put further raw data here, for example the SMTP dialogue or the transferred zone in the zone transfer test. Each block has a Kopieren (copy) button at its top right.

The raw data is where you look when a finding doesn’t match what you expected: it shows exactly what the server answered.

Befehl (command)

The dig commands that reproduce the result in the terminal, each command once. Queries over DNS over HTTPS appear as dig +https @…. If a check doesn’t query DNS at all, such as a pure HTTP check, you’ll see Dieser Check hat keine DNS-Abfragen gestellt. (this check made no DNS queries).

Since the last run

When you check the same input with the same tool a second time, the app compares the result with the previous run from the history. If anything changed, a line appears above the result, for example:

Seit dem letzten Lauf: 1 neue, 2 entfallene Befunde. (Since the last run: 1 new, 2 dropped findings.)

The comparison looks at the statement and level of each finding. A finding that moves from warning to OK therefore counts as one dropped and one new finding. If nothing changed, the line doesn’t appear. That way you see right after a change to DNS or a mail server whether it worked.

Exporting

The share icon on the right of the header (Exportieren, export) offers four options:

Entry	Result
Als JSON kopieren	the complete report as JSON on the clipboard
Als JSON speichern …	the same as a file
Als CSV speichern …	findings and all tables, separated by semicolons, the way Excel expects it in Germany
Als PDF für Kunden …	a designed report with an inwendo footer, meant for customers

The JSON contains the subject, timestamp, overall level, all findings with explanations, all tables and the dig commands. It’s good for archiving and for further processing in scripts.

The PDF shows the overall result, all findings with explanations and the tables, but no raw data. It’s meant for people who don’t want to read dig output. The full domain report adds a colour-coded overview of all sub-checks.