Domain Intelligence & Monitoring API
Check a domain from DNS to TLS to mail authentication. The tools cover DNS records, subdomain takeover, SPF, DMARC and DKIM, certificates, security headers, WHOIS and subdomains. They are free without an API key and work over REST and as MCP tools, for developers and AI agents. With a Pro key you can also monitor a domain and read its change events. The recon tools (subdomains, certificates, WHOIS) double as OSINT.
What you can ask
dns_lookup. The DNS records of a domain: A, AAAA, MX, NS, TXT, CNAME, SOA and CAA. API docs
dns_takeover_check. Whether a dangling CNAME lets someone take over a host name. API docs
email_auth_check. SPF, DMARC, DKIM, MX and MTA-STS checks, each pass, warn or fail. API docs
email_address_check. Whether the domain of an e-mail address takes mail, and whether the address is disposable. No mail is sent. API docs
ssl_check. The TLS certificate and TLS settings of a host on port 443. API docs
headers_check. Rates the security headers of the home page of a host. API docs
whois_lookup. The registration of a domain over RDAP or WHOIS: registrar, dates, status, name servers, DNSSEC. API docs
wayback_lookup. When the Wayback Machine captured the home page of a host. API docs
cert_search. The unexpired certificates that Certificate Transparency logs hold for a host name, as far as the first 5 pages of Cert Spotter show. API docs
subdomain_enum. The subdomains of a domain from Certificate Transparency and DNS. API docs
Example
curl https://api.contrastcyber.com/dns_takeover_check/shop.example.comExample response, trimmed; the values are an example:
{
"hostname": "shop.example.com",
"cname": "shop-example.cloudapp.net",
"chain": ["shop-example.cloudapp.net"],
"target_exists": false,
"dangling": true,
"provider": "Microsoft Azure",
"takeover_possible": true,
"summary": "shop.example.com points to shop-example.cloudapp.net, which does not exist. Microsoft Azure lets anyone claim that name, so shop.example.com can be taken over."
}From an agent
Your agent calls these MCP tools: dns_lookup, dns_takeover_check, email_auth_check, email_address_check, ssl_check, headers_check, whois_lookup, wayback_lookup, cert_search and subdomain_enum. Connect once with the MCP setup, then ask in plain words.
- “Is shop.example.com open to subdomain takeover?”
- “Does example.com have a valid DMARC policy and an SPF record?”
- “List the subdomains of example.com and check which certificates expire soon.”
Limits
Without a key you get 30 credits per hour. A Pro key gets 500 credits per hour. These tools have no bulk form.
Monitor it
A Pro key can watch a domain. Add an item with watchlist_edit. Then read its change events with watchlist_events. You pull the events when you want them.
A dns_lookup item gets a DNS scan of its name once a day. An ssl_check item gets a TLS scan once a day. A whois_lookup item gets an RDAP/WHOIS scan once a week, and once a day within 30 days of the registration’s end. A headers_check item gets a headers scan once a day: it reads the site’s robots.txt, and then its home page unless robots.txt disallows it. A cert_search item gets a certificate scan once a day. A change becomes an event after a later scan sees it again, except a new certificate issuer, which becomes an event at once. A problem that the first scan of a new dns_lookup, ssl_check or whois_lookup item reads becomes an event at once. The first scan of a new headers_check or cert_search item only sets its baseline and writes no event.
Each item watches one endpoint. The endpoint sets the events the item can emit:
| Watched endpoint | Events |
|---|---|
dns_lookup | domain_not_found domain_found ns_changed mx_changed ip_address_not_public ip_address_lost ip_address_restored cname_takeover_detected cname_takeover_resolved email_auth_degraded hosting_changed |
ssl_check | cert_expiring cert_invalid cert_listed tls_downgraded |
whois_lookup | domain_expiring registrar_changed transfer_lock_removed dnssec_disabled |
headers_check | security_header_removed |
cert_search | cert_unexpected |
See pricing for the Pro key. The security monitoring page lists every watched endpoint and its events.
Data sources
- DNS, TLS and header checks: asked live when you call.
ssl_checkandheaders_checkkeep an answer for one hour. A watcheddns_lookupitem makes the server ask DNS in the background, and a watchedssl_checkitem makes it open a TLS handshake in the background. A watchedheaders_checkitem makes it read the site’srobots.txtand home page once a day. - RDAP and WHOIS registries: asked live.
whois_lookupkeeps an answer that holds a registration for one hour. A watchedwhois_lookupitem makes the server ask the registry in the background. Each registry sets the terms of its own server. - Wayback Machine (Internet Archive), CDX server: Internet Archive Terms of Use. Asked live. An answer is kept for one day.
- Cert Spotter (SSLMate): SSLMate Terms of Service. Asked live. An answer is kept for one day. A watched
cert_searchitem makes the server ask in the background. - Can I take over XYZ?: CC BY 4.0. Local copy, used by
dns_takeover_check. - disposable-email-domains: CC0 1.0. Local copy, used by
email_address_check. - SSL Blacklist (abuse.ch): CC0 1.0. Local copy, used by
ssl_check. - SecLists (MIT) and commonspeak2 (Apache-2.0): the common names of
subdomain_enum.
FAQ
- Does the domain API need a key?
- No. Every domain tool works without a key, within the hourly credit limit. Only monitoring needs a Pro key.
- Can it find subdomain takeover risks?
- Yes. dns_takeover_check follows the CNAME chain of a host name. For the services it knows, it says whether a dangling CNAME can be taken over.
- How do I check SPF, DMARC and DKIM?
- Call email_auth_check with a domain. Each check comes back as pass, warn or fail. Add dkim_selector to check one DKIM selector.
- Can I watch a domain for changes?
- Yes, with a Pro key. Add the domain with watchlist_edit and read the change events with watchlist_events.