01
Create a read-only credential
Create the credential in Mailgun with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
Read-only checks on Mailgun verify your sending domains are active and that SPF and DKIM records actually validate, the email posture that phishing controls depend on.
3 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Connectivity check: confirms the Basic key authenticates against the chosen region host and lists domains (HTTP 200). A non-200 (e.g. 401) indicates an invalid key or the wrong region host.
account-connectivity
Fails if any Mailgun sending domain is not in the `active` state (e.g. unverified or disabled). Also fails if no domains are returned, to avoid a vacuous pass. Reads up to 1000 domains in one page (the endpoint uses numeric skip/limit paging, which the check DSL cannot express).
domains-active
Fails if any of the sending DNS records (SPF TXT, DKIM) for the specified domain do not resolve as valid. Also fails if no sending DNS records are returned, to avoid a vacuous pass.
domain-dns-valid
Bring your current platform's test list — we'll map it against these checks, gap by gap
Setup is minutes, not a migration project — and every step stays on your side
Create the credential in Mailgun with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.
Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.
Open any page for its full check register.
You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.
Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to Mailgun and remediates nothing silently.
A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.
Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.
20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.