is it DNS?
Live DNS from an independent seat: dig any public resolver, audit or sweep a domain, walk a delegation, read the resolver board.
- Category
- Developer Tools
- Primary Subcategory
- Observability, Monitoring & Incident Response
Integration details
Description
isitdns is a DNS looking glass with monitors. Every answer is a live measurement from the isitdns seat, stamped with the time it was read and where it was read from, never a cached or mocked result. Tools: dig asks any public resolver, or any public address, for a record over DoH, DoT, or Do53 over TCP or UDP, with DNSSEC, CD, ECS, NSID and RD=0 as knobs, and returns the answer in the shape dig prints plus the JSON. check_domain runs eleven checks on a domain (delegation, DNSSEC chain, DS against a live DNSKEY, glue, recursion policy, mail posture, TTLs, TCP fallback) and reports what each found, with no score and no grade. trace walks the delegation from the root. sweep_domain asks every authoritative nameserver of a zone the same questions with recursion off and compares them server by server, with CAA and ACME DNS-01 readiness. resolver_status is the live board of public resolvers with the verdict of every isitdns seat that voted this round; resolver_history is their incident record; dns_events is the days several resolvers were unhealthy at once; top_domains is the daily health of the domains isitdns monitors; ksk_board is the RFC 8509 root key sentinel across those resolvers. Prompts walk the tools in order for the common questions: why a domain does not load, whether something is intercepting DNS, whether a zone's DNSSEC is right, and whether public DNS is having trouble right now. Each keeps the answer scoped to this name, these resolvers and this moment. Free, no account, no key. Read-only: nothing here changes any DNS. Rate limit 100 tool calls a minute per address. Documentation at isitdns.net/agents.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Primary Subcategory
- Observability, Monitoring & Incident Response
- Secondary Subcategories
- None listed
- Brand
- isitdns
- Access
- No account required
- First tracked
- 2026-09-27
- Tool count
- 9
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competing in Claude Observability, Monitoring & Incident Response
View Category9 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are is it DNS? alternatives on Claude?
As of 2026-09-28, is it DNS? competes with Datadog, incident.io, Coralogix, PagerDuty, Bronto, Vercel, Sentry, Honeycomb, Railway, Steadybit, Elastic Cloud Serverless, Origin, Subtext, Adzviser Google PageSpeed Insights, AlertKick, Axiom, Beaam, InBrief, Lightrun, LogRocket, MonoDuty, ohdear.app, openstatus, Orb, Raygun, Resolve AI, Sentinel, Stealthium, Tsuga, Uptimely, UptimeRobot, Watchgoose in Claude Observability, Monitoring & Incident Response, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.