
How
≈ 31visits/mo
Use not read yet · estimate, read Oct 20, 2026
- For
- Developers and AI agents needing domain checks via API, MCP, or per-request payment.
- Runs as
- API
- Used for
- check a domain's DNS, WHOIS, TLS and email auth records
- look up whether a domain is blacklisted or recently registered
- monitor a page for changes since the last snapshot
- On the web since 2006, older than 98% of its shelfINITE Atlas
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantshow.is ↗
- MCP serveris.how/domain-intelverified in the MCP registry
- Stateanswers, 16 toolschecked 2026-10-20
- Address to connecthow.is/mcp
- OpenAPI spec16 pathsthe spec ↗
- API docshow.is/v1the vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Figure and bar: visits/mo, estimate · year: online since
- #1

Balou Tools
Checks a domain's DNS, TLS, mail authentication, security headers, SEO and performance, and scores the findings with recorded evidence.
35 linking domainsFrom ≈ $35/mo - #2

CobytesMCP · open
Scans a domain's DNS, email authentication and web security records, reporting failing checks with readable fix guidance.
97ActiveFree2024
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use How for?
Sign in to leave a noteWhat is How?
Returns DNS, WHOIS, TLS, DNSSEC, email auth, blacklist and uptime checks for a domain via card-paid API or per-request USDC payments. It is listed in the Atlas under Developer tools.
Who is How for?
Developers and AI agents needing domain checks via API, MCP, or per-request payment.
What are alternatives to How?
In Developer tools, by use: Balou Tools, Cobytes.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.