Inspect the transport, header, MIME, body-alternative, authentication-claim, attachment, remote-resource, and calendar layers of messages.
An email or calendar invitation is a nested machine-readable object whose envelope, headers, MIME tree, plain and HTML bodies, authentication claims, attachments, and scheduling properties may differ from the compact view shown to a person.
The submitted report remains byte-identical. This separate review, checked 2026-08-26, narrows implementation claims and gives visitors a decision path before they generalize from a local result.
Output produced deterministically by the local runtime.
Useful model or subset that must not be mistaken for full conformance.
Conclusion that needs an exact implementation, trust system, model, parser, or human review.
| Question | What the local page can answer | What it does not establish | Next evidence step |
|---|---|---|---|
| What headers, boundaries, URLs, and calendar properties are present? | The bounded mapper reports the selected syntax exactly. | Complete RFC conformance or client interpretation. | Use a conforming parser and preserve the raw message. |
| Did DKIM or DMARC pass? | No live validation is performed. | Signature, DNS, alignment, policy, or reputation. | Use an approved mail-authentication verifier and record inputs. |
| Will a calendar client execute an action? | The lab only identifies selected METHOD and property syntax. | Client auto-processing or user-interface behavior. | Test the exact client with side effects disabled. |
Shows body-branch, URL, authentication-claim, and scheduling-property differences.
Expected boundary: The parser inventories structures without sending, fetching, authenticating, or scheduling.
Open prepared laboratoryNo single view is automatically authoritative. Preserve the source, identify each parser or receiver, and compare their outputs before authorizing a consequential decision.
SMTP sender and recipients used for routing.
Display identities, trace fields, identifiers, dates, and claims.
Multipart structure, alternatives, attachments, and transfer encodings.
The client-selected plain, HTML, or related representation.
SPF, DKIM, DMARC, ARC, and Authentication-Results requiring context and verification.
VEVENT, recurrence, attendees, methods, alarms, and application behavior.
The workflow preserves evidence before transformation and keeps structural inspection separate from execution, remote verification, or model behavior.
These controls are contextual. They reduce a defined risk; they do not guarantee safety, truth, attribution, or resistance to every adaptive attack.
Disable remote image loading and external relationship resolution by default.
Compare plain and HTML body representations rather than selecting one silently.
Keep displayed sender, envelope sender, signing domain, and alignment status distinct.
Bound MIME nesting, decoded size, line length, and recurrence expansion.
Never let email or calendar text directly authorize an AI tool action.
Definitions are linked into the site-wide glossary and back to the full report.
Multipurpose Internet Mail Extensions for typed and multipart message bodies.
A MIME container offering alternate representations of the same content.
A transport representation such as Base64 or quoted-printable.
A domain signature over selected message headers and body data.
A policy relating authenticated domains to the visible From domain.
A chain preserving authentication results through intermediaries.
A structured format for events, tasks, time zones, and scheduling properties.
An RRULE defining repeated calendar instances.
An identifier allowing one MIME part to reference another inline.
These links are provided for visitors who want the governing specification, paper, framework, or implementation documentation. Links open in a new tab; the site does not fetch them during runtime analysis.
Message headers and body syntax.
Normative or first-party specification material.Media types and transfer encodings.
Normative or first-party specification material.Domain signature format and validation model.
Normative or first-party specification material.Current DMARC core protocol referenced by the submitted report.
Normative or first-party specification material.Authentication-result preservation through intermediaries.
Normative or first-party specification material.Calendar object syntax and recurrence.
Normative or first-party specification material.Defensive guidance for phishing risk reduction.
First-party guidance, framework, registry, or standards-program material.Email and web security directives.
First-party guidance, framework, registry, or standards-program material.The full submitted report is preserved byte-for-byte in the governed research library and in durable repository documentation. The laboratory turns selected concepts into deterministic local output without external calls or hidden persistence.
A structural analysis of Internet Message Format, MIME nesting, alternative bodies, authentication claims, remote resources, iCalendar actions, collaboration metadata, indirect prompt injection, and safe offline parsing.
Read governed reportParse bounded pasted message or iCalendar source, map headers and MIME parts, decode inert transfer encodings, compare body alternatives, and identify scheduling actions without sending, fetching, or live authentication checks.
Open bounded laboratory