Reception boundaries
The receiving layer applies limits before report processing begins.
- Maximum SMTP message and accepted attachment size.
- Maximum compressed and expanded payload sizes.
- Maximum archive nesting and file count.
- Accepted media types and report formats only.
- Timeouts and resource ceilings for parsing.
Separation and least privilege
Reception, raw storage, parsing and the customer-facing application are separable components. This allows the internet-facing receiver to be scaled or isolated without giving it broad application access.
- Private object storage for accepted originals.
- Application sessions and password hashing are handled separately.
- Account access is limited to domains associated with that account.
Data minimisation
The service requests aggregate reports through rua. It does not ask customers to configure forensic failure reporting through ruf. Aggregate data can still reveal sending infrastructure and business relationships, so it is handled as sensitive operational data.
Reporting a concern
Email security@dmarcanalyst.com or use the contact form and choose Security concern. Do not include passwords, report files or exploit payloads in the first message. We will provide a suitable follow-up channel.
The service is in private testing. Security controls and documentation will continue to be reviewed before wider availability.