DNS CHECKER

unreachable

Review how a host serves HTTP and HTTPS: redirects and security headers, scored.

DataBasex402 v2exactzzx.lt ↗︎

Settled via Coinbase.

Not seen in any discovery source since 2026-11-15.

All recent payment-challenge probes failed.

Transactions · 30d
1
Volume · 30d
$0.009
Unique buyers · 30d
2
Uptime · 30d
0.0%
Latency p50
—

Endpoints (7 live)

  • GET /mcp — Review how a host serves HTTP and HTTPS: redirects and security headers, scored. (0.029 USDC on Base)
  • GET /api/v1/domains/:domain/http-security — Review how a host serves HTTP and HTTPS: redirects and security headers, scored 0-100. (0.029 USDC on Base)
  • GET /api/v1/domains/:domain/dns-health — Diagnose the DNS setup of a domain and score it 0-100 (grade A-F). (0.029 USDC on Base)
  • GET /api/v1/domains/:domain/ssl — Review the TLS certificate and configuration of a host, scored 0-100 (grade A-F). (0.029 USDC on Base)
  • GET /api/v1/domains/:domain/availability — Can this domain be registered? Evidence-based state with source and warnings. (0.009 USDC on Base)
  • GET /api/v1/domains/:domain/email-security — Review how well a domain protects its e-mail, with score, grade and fixes. (0.029 USDC on Base)
  • GET /api/v1/domains/:domain — Full report on one domain: WHOIS registration data plus live DNS and mail records. (0.019 USDC on Base)

MCP tools (9)

DNS Checker https://d.zzx.lt/mcp

  • are_registered — Is each of these domains registered? is_registered for many names at once. Returns one item per unique domain in input order with `registered` (true / false / null = unknown), `status`, `source` and, for unusable input, an `error` code such as invalid_domain. One bad entry never fails the list. Domains that have name servers are answered from DNS alone; the others are confirmed with the registry, so a long list of unregistered names takes longer.
  • check_dns_health — Diagnose the DNS setup of a domain and score it 0-100 (grade A-F). Pass the zone apex (the registrable domain). It queries the domain's own name servers directly and checks: delegation at the parent, at least two name servers, that each server answers and is authoritative, SOA serial consistency, agreement between the parent's NS set and the zone's, response time, CNAME mistakes (CNAME at the apex, dangling www), CAA syntax and DNSSEC validation. `data.issues` lists problems with a stable `code`, a `severity` (critical, warning, info), the evidence and a fix; `data.recommendations` is the distinct list of fixes, most severe first. A check with status 'incomplete' could not finish and is not counted as passed; 'not_tested' was skipped (for example TCP without deep=true). The score is deterministic: the same findings always give the same score for a given `rules_version`. Reading the result: check status 'advisory' means nothing is wrong but an optional improvement is open; 'coverage_pe
  • check_domain — Full report on one domain: registration (WHOIS) plus live DNS. Use this when you need the whole picture: status (taken / available / unknown), registrar, creation, update and expiry dates, warnings such as an approaching expiry, and DNS records (NS, A, AAAA, MX, TXT, CNAME, SOA, CAA) with their TTLs, name server and mail host IPs, www, SPF, DMARC and DNSSEC. If WHOIS is unavailable the DNS part is still returned and a warning explains what is missing. `status` is decided by the same logic as is_registered and check_domain_availability (see `status_source` and `status_reason`), so the tools never disagree about one name. For only "is it registered?" use is_registered; to judge DNS quality use check_dns_health; for mail authentication use check_email_security.
  • 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).
  • check_domains — Run check_domain on many domains in one call (full reports, bounded parallelism). Returns one item per unique domain in input order. An item holds either `info` (the same report check_domain returns) or an `error` code such as invalid_domain, so one bad name never fails the batch. Use are_registered instead when you only need registration yes/no for many names.
  • check_email_security — Review how well a domain protects its e-mail, with score, grade and fixes. Checks SPF (single record, valid syntax, the 10-DNS-lookup limit counted through includes, strictness of 'all'), DMARC (policy p/sp, pct, alignment, report addresses), DKIM for the selectors you name (key present, RSA strength), MX and null MX, MTA-STS and TLS-RPT. Returns one section per mechanism plus `issues` (stable `code`, `severity`, evidence, fix) and `recommendations`. A check with status 'incomplete' (a DNS lookup failed) is not counted as passed, and 'not_tested' means it was skipped (DKIM without selectors); neither is a pass. It does not send mail and cannot know which selectors a sender uses: ask the user or inspect a message header 'DKIM-Signature: s=<selector>' if you need DKIM covered. Reading the result: check status 'advisory' means nothing is wrong but an optional improvement is open; 'coverage_percent' says how many checks ran to a verdict, so a high score with low coverage is a good result
  • check_http_security — Review how a host serves HTTP and HTTPS: redirects and security headers, scored. Use it to answer "does this site force HTTPS and send the standard security headers?". It fetches https:// and http:// of the host (public addresses only, response heads only; redirects are followed and reported) and checks HTTPS reachability, that http:// redirects permanently to https://, the redirect chain (loops, downgrades) and the headers of the final HTTPS response. Baseline headers (Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options) missing is a warning; contextual headers (Referrer-Policy, Permissions-Policy, framing protection) missing is advice only (`data.headers[].category` says which). A missing header is a hardening gap, not a vulnerability by itself, and none is critical. If HTTPS cannot be fetched, header checks are 'incomplete', not passed. For the certificate itself use check_ssl. Reading the result: check status 'advisory' means nothing is wrong but an optional
  • check_ssl — Review the TLS certificate and configuration of a host, scored 0-100 (grade A-F). Use it to answer "is this site's HTTPS healthy?" or "when does the certificate expire?". It connects to the host (public addresses only) and checks: certificate dates and expiry warnings (`data.days_remaining`), host name match, chain validation against public roots (self-signed and untrusted chains have their own issue codes), key size and signature hash, which TLS versions the server accepts (TLS 1.0/1.1 are flagged) and whether weak ciphers are accepted. `data.protocols` maps each version to true, false or null (null = this service could not test it); checks with status 'not_tested' or 'incomplete' are not counted as passed. If no handshake is possible you get `success: false` with `error.code` TLS_HANDSHAKE_FAILED; a target the service may not contact gives TARGET_NOT_ALLOWED, PORT_NOT_ALLOWED or DNS_ERROR. For HTTP headers use check_http_security. Reading the result: check status 'advisory' means no
  • is_registered — Is this domain registered? Answers true, false or null (unknown) with the evidence. `registered` is true when registration is confirmed (name servers are delegated, or the registry has a record), false only when the registry reliably reports no record, and null when no source could say. A missing DNS record alone never produces false. `status`, `source` and `reason` explain the answer. Subdomains are reduced to their registrable domain. Use check_domain_availability when you also need warnings and timestamps, for example before telling someone a name is free to register.

First seen · last seen · last active