checker-caa/checker
Pierre-Olivier Mercier 2c1eb7560c checker: expose standalone /check route via CheckerInteractive
Implements RenderForm/ParseForm on the provider: users can hit /check
with just a domain name; ParseForm resolves CAA records via direct DNS
queries (walking up the label tree per RFC 8659) and hands the SDK a
synthetic service payload so the standard Collect → Evaluate pipeline
runs without a happyDomain host. TLS probes are not gathered here, so
the rule reports StatusUnknown for the TLS cross-check in this mode.
2026-04-23 22:11:10 +07:00
..
ccadb.go Initial commit 2026-04-23 21:52:51 +07:00
ccadb_test.go Initial commit 2026-04-23 21:52:51 +07:00
collect.go Initial commit 2026-04-23 21:52:51 +07:00
definition.go Initial commit 2026-04-23 21:52:51 +07:00
interactive.go checker: expose standalone /check route via CheckerInteractive 2026-04-23 22:11:10 +07:00
provider.go Initial commit 2026-04-23 21:52:51 +07:00
rule.go checker: migrate Evaluate to per-subject []CheckState 2026-04-23 22:11:06 +07:00
rule_test.go checker: migrate Evaluate to per-subject []CheckState 2026-04-23 22:11:06 +07:00
tls_related.go Initial commit 2026-04-23 21:52:51 +07:00
types.go Initial commit 2026-04-23 21:52:51 +07:00