SiteTriage

Look up DNS records for a domain and explain them in plain language. Use this when a user asks what a domain resolves to, whether a record exists, or to inspect A/AAAA/CNAME/MX/TXT/NS/CAA/SOA records. Accepts a bare domain or a URL. Returns the raw answers plus an interpretation of what each result means for the site's operation. For a full site diagnosis prefer diagnose_site; use this when you need one specific record type.

dns_lookup

Compare a domain's DNS answers across multiple independent public resolvers (Cloudflare, Google, Quad9) to detect whether a recent DNS change has propagated. Use this when a user just changed an A record, moved hosts, or says 'it works for me but not for others'. Reports each resolver's answer and flags divergence (e.g. 'Google still returns the old IP, propagation is incomplete'). Because different resolvers cache for different times, disagreement means the change is still rolling out.

dns_propagation

The main entry point. Given a URL or domain, run a complete website health triage from the edge and return a ranked diagnosis: what is broken, the most likely root cause(s) in order of confidence, and concrete step-by-step fixes. Covers DNS resolution (including apex-vs-www and CNAME problems), propagation across resolvers, the live TLS certificate (expiry, hostname match), the HTTP status and redirect chain with latency, security headers, email authentication (SPF/DMARC) and domain registration/expiry. Use this first whenever a user says 'my site is down', 'my site broke after deploying', 'why is my cert failing', or gives a URL and asks what's wrong. Prefer this over calling the individual tools one by one; use the specific tools only to drill into a single dimension afterwards.

diagnose_site

Look up a domain's registration details via RDAP (the modern JSON replacement for WHOIS): registrar, creation/expiry dates, days until the domain expires, registrar-lock statuses, nameservers, and whether DNSSEC is enabled. Use this when a user asks who registered a domain, when it expires, why it 'stopped working' (an expired domain takes the whole site and email down), or to confirm the nameservers at the registrar match where DNS is actually hosted. Queries are made over HTTPS to the authoritative registry.

domain_info

Check a domain's email authentication setup — SPF, DKIM and DMARC — and explain in plain language why mail from the domain might be landing in spam or being spoofed. Use this whenever a user says their emails go to spam, aren't delivered, or asks whether their domain is protected against spoofing. Reads only DNS TXT records (no mail is sent). DKIM selectors vary by provider; pass known selectors via 'dkimSelectors' or let the tool try a broad set of common ones (Google, Microsoft 365, SendGrid, Mailchimp, Zoho, Proton, SES, Fastmail, …). Returns pass/fail interpretation and concrete fix steps.

email_auth_check

Probe a URL over HTTP(S) from the edge and report the status code, the full redirect chain, response time, response headers, and common misconfigurations (redirect loops, HTTPS→HTTP downgrades, missing security headers). Use this when a user reports the site is down, returns the wrong status, redirects endlessly, or 'the www version doesn't work'. Redirects are followed manually with SSRF checks at every hop. Accepts a URL or a bare domain (treated as https://). Returns concrete findings, not guesses.

http_check

Inspect a site's live TLS certificate: issuer, validity window, days until expiry, and whether the certificate actually covers the hostname (SAN/CN match). Use this when a user reports a certificate warning, 'your connection is not private', an expired-cert error, or a name-mismatch. Connects to the host over TLS and reads the certificate the server presents right now (not a cached or historical one). Note: on some TLS 1.3 endpoints the certificate flight is encrypted and detailed fields cannot be read; in that case the result says so and still confirms whether the chain is trusted.

ssl_check