DNS Checker: read-only domain intelligence from public sources (DNS, RDAP, WHOIS, TLS, HTTP). Pick the tool by question. 'Tell me about this domain': check_domain (one) or check_domains (many). 'Is it registered?': is_registered (one) or are_registered (many); 'can I register it, and how sure are you?': check_domain_availability. 'Is its DNS healthy?': check_dns_health. 'Is its e-mail protected (SPF, DMARC, DKIM)?': check_email_security. 'Is its HTTPS and certificate healthy?': check_ssl. 'Does it force HTTPS and send security headers?': check_http_security. Results never guess: unknown / null / not_tested / incomplete mean the data was unavailable, not that the check passed. A check marked advisory has an optional improvement open; coverage_percent shows how many checks ran. Pass bare domain names, not URLs.
9 verified, 0 failed, 0 observed risk, 1 not checked, on 15 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-15 | 143 | 228 | 10 |
Every x402 payment we hold to the address the catalogue lists for this server’s paid tools (0x7d09…5354), payments an address made to itself left out. The same address takes payment for 6 other catalogued services, so these figures are an upper bound for this server.
9 tools on the last day the list was read, fingerprint 5d813883f2df766d61a.
Check domain availability
Can this domain be registered? Evidence-based state with source and warnings. `data.status` is one of: registered; unregistered (the registry has no record, usually confirmed by a second source); reserved (the registry holds the name back); unknown (sources failed or disagree; do not claim the name is free); unsupported_tld (no registry data exists for this TLD). `data.source` names what decided it (dns, rdap, whois, rdap+whois). `data.warnings` lists weaker evidence, for example single_source. Treat 'unregistered' with a single_source warning as likely, not certain, and re-check at the registrar before buying. The input is reduced to its registrable domain (www.example.co.uk is checked as example.co.uk).
read-onlyadditive onlysafe to repeatreaches outside servicesas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| domain | string | yes | A bare domain name such as 'example.com'. Unicode (IDN) names are accepted. Do not pass URLs, paths, ports or e-mail addresses. |
No agent registration names this server; we probe it on our own list.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 15 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-15 | Some runs failed | 13 | hourly runs |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 15 November 2026, 23:00 UTC: 5 of 5 requests answered, p50 123 ms, p95 228 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-16 00:00 (now) | — | 0 | 0 |
| 2026-11-15 23:00 | 123 | 1 | 0 |
| 2026-11-15 22:00 | — | 0 | 0 |
| 2026-11-15 21:00 | 143 | 1 | 0 |
| 2026-11-15 20:00 | 140 | 1 | 0 |
| 2026-11-15 19:00 | 154 | 1 | 0 |
| 2026-11-15 18:00 | 164 | 1 | 0 |
| 2026-11-15 17:00 | — | 1 | 1 |
| 2026-11-15 16:00 | — | 1 | 1 |
| 2026-11-15 15:00 | — | 1 | 1 |
| 2026-11-15 14:00 | 159 | 1 | 0 |
| 2026-11-15 13:00 | 122 | 1 | 0 |
| 2026-11-15 12:00 | 197 | 1 | 0 |
| 2026-11-15 11:00 | 161 | 1 | 0 |
| 2026-11-15 10:00 | 136 | 1 | 0 |
| 2026-11-15 09:00 | — | 0 | 0 |
| 2026-11-15 08:00 | — | 0 | 0 |
| 2026-11-15 07:00 | — | 0 | 0 |
| 2026-11-15 06:00 | — | 0 | 0 |
| 2026-11-15 05:00 | — | 0 | 0 |
| 2026-11-15 04:00 | — | 0 | 0 |
| 2026-11-15 03:00 | — | 0 | 0 |
| 2026-11-15 02:00 | — | 0 | 0 |
| 2026-11-15 01:00 | — | 0 | 0 |