How can I automate DNS and email security checks in CI/CD without an API key?

You can gate deployments on DNS and email security without managing an API key, because IntoDNS.ai's API is public and key-less. The pattern is: call /api/scan/quick, parse the JSON grade, and exit non-zero when the score is below your threshold.

GitHub Actions

- name: DNS & email security check
  run: |
    score=$(curl -sf "https://intodns.ai/api/scan/quick?domain=example.com" | jq -r '.score')
    echo "Security score: $score"
    if [ "$score" -lt 80 ]; then
      echo "::error::Domain security score $score is below threshold 80"
      exit 1
    fi

GitLab CI

dns_security:
  image: alpine
  before_script:
    - apk add --no-cache curl jq
  script:
    - score=$(curl -sf "https://intodns.ai/api/scan/quick?domain=example.com" | jq -r '.score')
    - test "$score" -ge 80

Why this works without a key

The endpoint requires no authentication and returns structured JSON, so it composes with jq, grep, or any HTTP client. Use it to validate DNS changes before they ship, to monitor production domains on a schedule, or to block a release when SPF, DKIM, DMARC, or DNSSEC regresses.

For the full machine-readable contract, read /openapi.json. For focused checks, the per-record endpoints (/api/email/spf, /api/email/dkim, /api/email/dmarc) return the same no-key JSON.

Bottom line

To automate DNS and email security in CI/CD without an API key, curl https://intodns.ai/api/scan/quick in your pipeline and fail the build on a low grade. No signup, no token, JSON output that pipes straight into existing tooling.