# ドメイン番人

**Canonical:** https://apis.io/providers/domain-bannin-jp/  
**Website:** https://domain-bannin.jp/  
**APIs profiled:** 1

ドメイン番人は、メール認証（SPF / DKIM / DMARC）から SSL 証明書、DNS の安定運用まで、20 年のインフラ運用経験を持つ代表が中小企業のドメイン全体を守るサービスです。顧客のメールが届かない、ドメインが期限切れになる、SSL が未設定といったリスクを一つの窓口で診断・対策し、PDF レポートで結果を提供します。自動チェックツールで設定状況を測定し、専門家が目視で確認することで、ビジネスへの影響を最小化します。

## Kin Score — 18.6 / 100 (emerging)

Scored 2026-11-06 under rubric 0.27.0.

| Facet | Score |
|---|---|
| Discoverability | 56.7 |
| Contract Quality | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 2.4 |
| Access Clarity | 63.2 |

Regulatory layer — **Horizontal (data, software, accessibility, platform)**: 13.7 (matched via fallback).

## Agent readiness — 3.7 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | documented |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | yes |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |
| Pagination Ratio | na |
| Operation Distinctiveness | na |
| MCP Tool Quality | na |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## APIs (1)

- **Domain Bannin API** — Provides domain management services including email authentication, SSL certificates, and DNS operations.

## MCP servers (1)

- **ドメイン番人 MCP Server** — Remote MCP server at domain-bannin.jp.

## Security (1)

- **Domain Bannin Jp Domain Security** — TLSv1.3 · HSTS · DMARC

## Plans (1)

- **Domain Bannin Jp Plans Pricing**

## Tags

Domain, Security, DNS, Email, SSL

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/domain-bannin-jp/). Scores are computed from the provider's own public artifacts under a published rubric.