Email Auth Coverage

Audit email authentication method coverage.

Description

Email authentication coverage tracks named checks such as those selected by a mail administrator.

Email authentication coverage tracks named checks such as those selected by a mail administrator. A recorded label does not prove a passing authentication result.^[1]

Audit email authentication method coverage.

When to use Email Auth Coverage

Use this tool to audit email authentication method coverage.

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.

How to use Email Auth Coverage and understand its results

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
Enter requiredMethods, configuredMethods using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
requiredMethods	Required email authentication methods	list of string	Required
configuredMethods	Configured methods	list of string	Required

Supply required and observed authentication labels. Enter a nonempty required list and an observed list, which may be empty. Trim and lowercase entries for comparison; blank entries are errors. Deduplicate by normalized key. Return matched/missing required labels, unexpected observed labels, and coverage. Required order is preserved; the last trimmed spelling wins for duplicate keys.

coverage%=100×matchedUnique/requiredUnique

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "requiredMethods": [
      "alpha",
      "beta",
      "gamma"
    ],
    "configuredMethods": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No message headers, DNS, signatures or live mail configuration are inspected.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Digital Security Checklist: Compare caller-supplied requirements and observations for digital security checklist. For a complementary task, use Onboarding Access Checklist: Compare caller-supplied requirements and observations for onboarding access checklist.

References

Email Auth Coverage — tool.io

Similar or alternative tools

Digital Security Checklist
Compare caller-supplied requirements and observations for digital security checklist.
Onboarding Access Checklist
Compare caller-supplied requirements and observations for onboarding access checklist.