CI/CD Email Security Check Kit
Submit your domain and CI target. Receive a repo-ready YAML, shell script, checklist, and sample failure output for baseline email DNS checks.
Built for teams that want practical guardrails before they integrate a full audit API.
Input
- domain,
- CI platform,
- strict or warn mode,
- records that should be release blockers,
- whether the domain sends production mail.
Output
- GitHub Actions YAML,
- shell script,
- Markdown checklist,
- sample failure output,
- notes on when an API-backed check is safer.
Packages
Basic Kit
Best for: baseline GitHub Actions/shell guardrail
- Basic workflow YAML
- Shell check script
- Markdown checklist
- Warning/fail-mode notes
Repo-Ready
Best for: stronger repo handoff
- Everything in Basic
- Stricter configuration notes
- Sample failure output
- Implementation guide
Team Pack
Best for: several domains/workflows
- Up to 3 domains/workflows
- Team-ready checklist
- Stricter gating guide
- API upgrade notes
Fixed-output policy
Veldica kits are fixed-output diagnostic products. This is a request-first pilot flow; Veldica will review whether the request fits the selected scope and contact you with next steps and a payment link if approved. No calls. No live troubleshooting. No DNS account access.
Sample output preview
Included files:
.github/workflows/email-dns-check.ymlscripts/check-email-dns.shdocs/email-dns-checklist.mddocs/email-dns-sample-failure.md
name: Email DNS checks
on:
pull_request:
paths:
- "dns/**"
jobs:
email-dns:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Check email DNS
run: scripts/check-email-dns.sh example.com --mode warn
Good Fit
This kit is useful when DNS changes move through pull requests, Terraform, or another review workflow. It gives the team a practical baseline for SPF, DMARC, MX, MTA-STS, and TLS-RPT checks.
Upgrade Path
Raw DNS checks are intentionally limited. Use the RapidAPI quickstart when you need structured JSON, recursive SPF lookup counts, DKIM selector-aware checks, fix-plans, or before-and-after comparisons.
on: closing_reports_hub :: ent: click_service location: closing_reports_hub ::
Keep Exploring
Use the Workflow Library to browse more guides, comparisons, and integration examples to continue your evaluation.
See the planned free checker scope before requesting the kit.
See the baseline checks this kit packages for a real repo.
Understand where shell checks stop and structured audit output starts.
Move from no-key checks to recurring API-backed automation.
Package the no-key baseline for your repo
Request the kit when you want the YAML, script, checklist, and failure output assembled for your CI target.