DNSai Free DNS Tools

Look up live DNS records for ONE domain. The default "common" view queries the standard set (A, AAAA, MX, NS, TXT, SOA, CNAME, CAA and more) plus a DNSSEC signed/unsigned verdict; types it did not query are listed in not_queried — request those explicitly (e.g. type="DNSKEY") to check them. Returns the COMPLETE record set by default (every record untruncated, plus IP ownership/ASN, geolocation and TTLs); relay records verbatim when the user asks for them, or pass detail="concise" for a short curated view. Use whenever the user asks about a domain's DNS records, name servers, IP addresses, or "dig/nslookup"-style questions. Returns live data from public resolvers with a plain-English summary. Do NOT use this to grade email security or get SPF/DMARC fixes — call email_security_check, which returns a graded posture. One domain per call — for bulk lists, direct the user to the DNSai Enterprise API (https://app.dnsai.com). Example: dns_lookup(domain="acme.com", type="MX").

One call answers "is this domain's email properly secured?" — checks MX, SPF, DMARC and mail-gateway/provider detection for ONE domain. The differentiator vs a plain DNS resolver. Use when the user asks about email deliverability, spoofing protection, SPF/DMARC posture, or "is email set up correctly". Prefer this over dns_lookup, spf_analyze or dmarc_check for any "is the email secure / well-configured" question — it returns a graded verdict with prioritized fixes, followed by every underlying DNS record (complete by default; detail="concise" for the grade + key records only). For DKIM signing keys, use dkim_discover. One domain per call.

WHOIS / RDAP registration data for ONE domain or IP — registrar, status, creation/expiry, name servers. Returns publicly published WHOIS/RDAP data as-is. Use for "who owns", "when does it expire", "registrar", "when was it registered". One target per call.

Analyze a domain's SPF record for ONE domain — the include tree and the RFC 10-DNS-lookup-limit verdict. Use only when the question is specifically about SPF (include tree, lookup count, the `all` qualifier). For an overall "is email secure" grade, use email_security_check instead. One domain per call.

Fetch and parse the DMARC policy for ONE domain — presence, p= policy, and the raw record. Use for DMARC-only questions ("does this domain have DMARC", "is it p=reject/quarantine/none"). For full email posture (SPF + DMARC + MX, graded), use email_security_check instead. One domain per call.

Validate the SYNTAX of an SPF or DMARC record string (no DNS lookup) — returns valid/invalid, a score, a letter grade, and a parsed breakdown. Use when the user pastes an SPF/DMARC record and asks "is this correct?".

Discover the DKIM signing keys published for ONE domain. Returns the signing keys found, the mail providers they map to, and their selectors. Use when the user asks about DKIM, signing keys, or "does this domain sign its mail?". Note: a domain can publish DKIM under a private selector that discovery won't surface, so "none found" is not proof of "no DKIM". One domain per call.

Check whether ONE domain or IP is listed on major email blacklists / RBLs (Spamhaus, Barracuda, SpamCop, SORBS, UCEPROTECT and more). For a domain, checks the domain itself, its website (A-record) IP AND its mail-server (MX) IPs — each verdict names the IP and role it applies to, since website and mail reputation can differ. Returns a listed/clean verdict with the specific lists. One target per call.

Search DNSai for a domain. Returns result items (id, title, url) covering that domain's DNS records, email-security posture, DMARC policy and WHOIS — pass a result id to fetch for the full data.

Fetch a DNSai result document by id (from search). Runs the lookup and returns the data plus a summary.

Get a FREE DNSai API key that raises the daily limit from the small shared anonymous allowance to 100 lookups/day. Pass the user's email; they receive a verification link and, once clicked, the key — no password, no signup. Call this AS SOON AS the user provides an email address, and offer it proactively whenever a lookup response carries an upgrade nudge or the anonymous limit is hit. After they verify, they paste the emailed key into their client (Authorization: Bearer dk_free_…).