Protection
turn clarity into a safer next step.

Findings only matter if they change what you do. A practical path from "I see a gap" to "my configuration is stronger today".

Public signals only. Encrypted in transit. Built for defensive use.
Back to the gallery
THE WORK IS REAL / 03Protection: turn clarity into a safer next step

The triage order that works

1. Fix what is clearly yours. If your own domain lacks SPF, DMARC, or correct MX records, that is a configuration task with a known fix — start there before anything else.

2. Check exposure you control. Software listed in a government exploited-vulnerability catalog and running on your systems is a patching priority, not an anxiety item. Catalog entries include the affected product for exactly this reason.

3. Watch, then block. For an address showing abusive behavior, match it against your own logs first. If it appears, block or rate-limit it at your firewall or edge — evidence-based, reversible, and documented.

Document everything

Keep the report, the timestamp, and the action you took. If you ever need to explain a block to a provider, a client, or a court, a dated evidence trail is what makes your decision defensible.

What protection is not

It is not retaliation, scanning someone else's systems, or contacting people behind addresses. Those actions create legal risk for you and are outside AUGI's purpose. Defense only — that boundary is what makes the tool safe to use.

General security education, not incident-response or legal advice for a specific event.

Explore a safer
next signal.