qzx checkDns

Representative output example

This illustrative JSON is derived from the current implementation-backed result contract. It shows what the command can return without claiming a recorded execution; values vary with inputs, host, permissions, and optional tools.

Example command: qzx checkDns google.com --json

{
    "success": true,
    "message": "Queries A, AAAA, MX, TXT, NS, and CNAME DNS records for a given domain. In this illustrative example, the command completed successfully.",
    "domain": "example.com",
    "errors": [],
    "records": {
        "A": [
            "192.0.2.10"
        ],
        "MX": [
            "10 mail.example.com"
        ]
    },
    "summary": {
        "status": "healthy",
        "items_checked": 4
    }
}

{
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "type": "object",
    "required": [
        "success",
        "message"
    ],
    "properties": {
        "success": {
            "type": "boolean"
        },
        "message": {
            "type": "string"
        },
        "domain": [],
        "error": {
            "type": "string"
        },
        "errors": [],
        "records": [],
        "summary": []
    },
    "additionalProperties": true
}

Errors and limits

The public contract requires success=false and a descriptive message on failure. This catalog does not yet declare a command-specific error taxonomy; inspect the result and do not invent error codes.

QZX is alpha software. Optional dependencies, permissions, and host capabilities can change the result.

Evidence workflow: requires an authorized endpoint or reviewed fixture.