Developer Updates

API Changelog

Track breaking changes, new features, and deprecations. We notify developers before making breaking changes.

Breaking changes are announced at least 12 months ahead. Read the versioning and deprecation policy.

RSS feed
Product update improvement

More WHOIS contact lookups succeed

  • WHOIS can now retrieve public contact details from some registrar referrals that previously timed out.
Product update improvement

More contacts from registrar RDAP

  • When a registry provides a matching registrar RDAP referral, WHOIS v1, v2 and bulk results can include public registrant, administrative, technical and billing contact details plus current abuse contacts; a failed or mismatched referral leaves the registry result unchanged.
Product update improvement

RDAP abuse contacts in WHOIS results

  • When available, WHOIS v1, v2 and bulk results now include email and phone details from RDAP entities with an abuse role, including nested registrar entities; v2 preserves RDAP values and uses traditional WHOIS abuse fields to fill any missing details.
Product update improvement

Website categorization recognises gambling sites

  • Website categorization has a new Gambling category (IAB36) with the subcategories Online Casino, Sports Betting, Poker, and Lottery & Bingo. Casino, betting and lottery sites used to be filed under unrelated categories such as SaaS & Cloud, News & Media or Technology. Gambling words are now also recognised in Japanese, Korean, Chinese, Russian, German, Spanish and Italian pages, and in the site's own name, such as bitcasino. The category appears in /v1/categorize, bulk results and /v1/categorize/taxonomy.
Product update fix

More accurate recipes, typo and health checks, and working job links

  • Job and batch responses now link to https://domscan.net. Before, status_url, results_url and the other job links pointed to a host that answered 404. Job and batch timestamps are now always valid ISO 8601.
  • Recipes accept trailing dots and internationalized names, reject unsupported TLDs and invalid numbers with a 400 error, and report a step that fails as unknown and refunded instead of turning it into a finding or advice. The due diligence recipe lists registrar prices again, and the competitor intelligence and infrastructure discovery recipes show the IP owner and country.
  • Typo tools reject URLs and unsupported TLDs, honour false values such as include_tld_swap=no, and permute internationalized names as Unicode. /v1/typos/threats and /v1/typos/report now look up DNS for registered lookalikes, so active threats are reported.
  • /v1/similarity compares internationalized names as Unicode and no longer flags unrelated short or numeric names as typosquats.
  • Health checks of a subdomain look up nameservers, DNSSEC and CAA on its registrable domain, no longer list CNAME targets as A records, and treat a null MX as no mail server. Bulk health checks bill a repeated domain once and refund invalid or failed items.
  • /v1/overview and /v1/report reject unsupported TLDs, and /v1/report rejects unknown section names instead of silently dropping them.
  • Watchlist checks report unknown instead of registered or available when a lookup gave no authoritative answer, a watchlist domain can be removed with the same spelling used to add it, and a batch webhook that points to a private address is rejected before any charge.
  • Brand logo URLs returned by /v1/brand and the MCP brand_lookup tool now point to https://domscan.net. Before, they pointed to a host that answered 404.
Product update fix

Correct rendered page reports, more complete link checks and fairer validation billing

  • Rendered page reports, /v1/onpage/render-diff and rendered scrape modes read the rendered page correctly again. Before, every rendered page was reported as empty, with no title or words.
  • Link checks, site audits and the other page analyses now read links on pages that end their link tags across several lines. Some pages showed only a fraction of their links.
  • Scrape text, Markdown and LLM output no longer merge the page title into the body text. Scrape and crawl jobs show an error only on failed items, stop retrying a target that redirects to a private address, and return valid ISO 8601 timestamps.
  • /v1/redirects accepts an uppercase scheme and surrounding spaces, rejects names that point to private addresses, and no longer charges when the host could not be reached or found.
  • /v1/ads-txt accepts one redirect to a hosted ads.txt service, as the IAB ads.txt specification allows, and /v1/site-audit no longer reports a successful crawl as fetch_failed.
  • /v1/agent-readiness no longer counts a generic HTML page returned for a missing file as an OpenAPI, MCP or OAuth document.
  • Phone bulk validation bills a repeated number once, and /v1/vat/validate rejects a requester that is not a valid EU VAT number and limits input length. National ID validation uses the default country when country is empty.
Product update fix

Accurate prices and valuations, Cloudflare detection and fairer bulk billing

  • Registrar price lists no longer show $0.00 placeholder register or renew prices or recommend them as the cheapest option. Real $0.00 transfer prices are kept.
  • /v1/prices/compare no longer reports a domain as unavailable when a registrar does not sell its TLD, and rejects a TLD that does not exist with a 400 error before any charge. POST /v1/prices/bulk rejects a malformed body or registrars list with a 400 error.
  • /v1/value rejects URLs, ports, unknown TLDs and invalid names with a 400 error instead of valuing them. /v1/value/bulk values and bills a repeated domain once and lists invalid items in errors without charging for them. /v1/score/compare accepts domains and ignores repeated names.
  • Technology and hosting detection now recognize sites served through Cloudflare, and technology scans accept a domain written with a trailing dot or in capital letters.
  • Bulk technology and categorization requests scan and bill a repeated target once. In categorization and hosting bulk requests, one invalid item no longer fails the whole batch. /v1/categorize checks min_confidence and accepts a trailing dot or an uppercase scheme.
  • MAC lookups name the actual company for addresses in shared IEEE blocks. IP lookups and /v1/company/resolve refund a temporary data outage instead of charging, and /v1/popularity reports an unusable rank as unknown.
  • Bulk social handle, reputation, URL intelligence and identity requests check and bill a repeated item once and do not bill invalid items. In URL intelligence and identity bulk requests, one invalid URL no longer fails the whole batch, and a request body that is not a JSON object now gets a 400 error instead of a server error. Email check bulk requests handle such a body the same way.
  • Social handle checks and domain profiles with no answer are refunded, .io and .biz profiles confirm a registry not-found answer before reporting a domain as unregistered, and reputation checks no longer flag internationalized domains as phishing because of the hyphens in their xn-- form.
Product update fix

More reliable email authentication tools and SSL checks

  • SPF flattening now follows nested includes and redirects, keeps qualifiers and a, mx, exists and ptr terms, and keeps any term it cannot safely flatten as written, with a warning. Before, the flattened record could leave out authorized senders.
  • The SPF and DMARC validators now report unknown mechanisms, invalid IP ranges, wrong versions, invalid tag values and more than one published record as issues. The SPF and DMARC builders reject invalid input with a 400 error instead of producing an invalid record.
  • DKIM checks read only the TXT record behind a CNAME selector, treat a key without the optional v=DKIM1 tag as present, report a selector whose lookup failed as unknown, and return 503 when DNS gives no answer.
  • Email checks accept internationalized domains such as user@münchen.de, reject unknown check names and bill a repeated address once. /v1/email-auth no longer charges when no record could be looked up.
  • SSL grade, audit and chain now detect servers that still accept TLS 1.0 and 1.1 and list a revoked certificate as an issue. SSL grade, chain, expiring and audit no longer charge when no certificate could be read.
  • /v1/certificates accepts 1/0 and yes/no for include_expired and include_subdomains, rejects an invalid limit, and no longer charges for or caches a reply when the certificate sources were unavailable.
Product update fix

More accurate availability, WHOIS and DNS answers, and no charge for lookups without an answer

  • Availability checks accept TLD lists written with a leading dot (.com), in any case, and check each TLD once. POST /v1/status/bulk checks and bills each domain once, returns available: null with an error for invalid input, and refunds every item without an answer.
  • WHOIS, RDAP, lifecycle and parking lookups that could not determine an answer are no longer charged. /v1/lifecycle now rejects URLs and invalid names, .io and .biz names pending deletion are no longer reported as available, /v1/whois/bulk bills a repeated domain once, and /v1/whois/history rejects an invalid limit.
  • DNS propagation checks no longer report a CNAME target as an A record, which could show a change as propagated when it was not.
  • DNS lookups that no resolver answered are refunded. /v1/dns/all lists record types without an answer in failed_types instead of showing them as absent, a null MX record is returned as ".", and bulk DNS, RDAP, certificate, hosting, profile, email authentication and subdomain lookups bill a repeated input once and refund invalid or failed items.
  • Subdomain verification also checks IPv6 (AAAA) records and returns verified: null when DNS gave no answer, instead of false.
  • /v1/idn rejects IP addresses and flags invisible characters as high risk, /v1/compare ignores repeated domains, and /v1/tlds accepts Unicode TLDs such as .рф and rejects unknown filter values.
Product update fix

MCP job creation, clearer batch errors and more accepted webhook URLs

  • MCP tools that create scrape, crawl, tech scan and domain discovery jobs or API batches now take an idempotency_key argument, which DomScan sends as the Idempotency-Key header. Scrape and crawl jobs require a key, so MCP clients could not create them before.
  • When POST /v1/batches rejects a request item, the INVALID_BATCH_ITEM error now includes the item index, a reason code such as path_missing or path_not_batchable, and an example of an accepted item.
  • Webhook URLs and page fetches now accept hosts that are themselves listed as private suffixes in the Public Suffix List, such as postman-echo.com and httpbin.org. They were rejected as an invalid URL format.
Product update fix

Names that are live in DNS are no longer reported as available

  • For extensions without RDAP, a registry can answer not found for a name it does not hold itself, such as a site run under a government second-level domain like justica.gov.pt. Availability checks, WHOIS and domain profiles used to report these names as available. When the registry answers not found, DomScan now also checks DNS for the exact name, and a name that has nameservers or resolves is returned as registered: true and available: false. Names under gov.pt that are not in DNS are now returned as unknown, because the .pt registry does not hold them.
Product update improvement

Higher rate limits, now listed on the pricing page

  • Free accounts can now make 300 API requests per minute, up from 120, and paid accounts 900, up from 600. Bursts stay at up to 60 requests on free accounts and 120 on paid accounts.
  • The pricing page now lists the rate limits for free accounts, paid accounts and Enterprise. Enterprise and the high-volume monthly plans get custom limits agreed to fit your workload.
Product update fix

Availability checks follow more registry rules

  • Availability checks no longer report names that registry rules hold back as available. ICANN-reserved names in new gTLDs and .org (such as example, nic and Olympic or Red Cross names), names with hyphens in the third and fourth positions, one-character .au names, invalid .br names and reserved .mx names now return available: false with an availability_reason (registry_reserved or invalid_name).
Product update feature

Larger watchlists, editable alert emails and email delivery for more alerts

  • Your watchlist limit now grows with your plan: paid plans can watch one domain for every 30 monthly plan credits, with at least 100 and at most 1,000, and GET /v1/watchlist shows your current limit as max_domains. Adds over the limit are refused and cost no credits.
  • You can now change the alert email of a watched domain with PATCH /v1/watchlist/:domain, without removing and adding it again, and each domain's own alert email is used for its alerts.
  • Certificate, DNS, lookalike, price and brand watchlist alerts can now also be sent by email: set notify_email on the alert subscription. Webhook delivery is unchanged.
Product update fix

Names a registry has reserved or blocked are no longer reported as available

  • Some registries answer a lookup for a name they hold back with a not-found response that explains why it cannot be registered, for example a registry reservation, a brand-protection block, a usage restriction or an invalid name. Availability checks, RDAP, WHOIS and lifecycle used to report these names as available. They now return available: false and registered: false with an availability_reason (registry_reserved, registry_blocked, registry_restricted or invalid_name) and the registry's own explanation in registry_message. Names the registry reports as simply not found are checked as before.
Product update fix

More accurate TLS, CAA and DNS migration results

  • Deep TLS scans no longer list a protocol as offered when the server reports it as not offered. A scan that could not read the server no longer comes back ready with empty sections, and TLS 1.3 support is reported as unknown instead of false when the scan found no evidence either way.
  • CAA checks now recognise an allowed issuer when the record carries extra parameters, such as pki.goog; cansignhttpexchanges=yes, so google_trust_services_allowed and similar fields are correct.
  • The DNS migration recipe no longer warns that DKIM and DMARC are missing when they are configured. When those lookups are inconclusive, the warning leaves them out instead of calling them missing.
  • DNS security scores are marked as partial when the blacklist lookups could not be completed, even if every scored check answered.
  • X-Credits-Remaining is left out of an uncharged response when the current balance is not known, instead of showing an earlier balance. Charged responses still report the balance after the charge.
  • MCP clients that connect from scripts and servers are no longer blocked before they sign in.
Product update fix

Direct .br names are no longer reported as available

  • The .br registry only accepts registrations under category suffixes such as .com.br, .net.br or .app.br, so a name like example.br cannot be registered. Availability checks and WHOIS used to report these names as available when no registration existed. They now return available: false with availability_reason closed_registry. Names under category suffixes, such as example.com.br, are checked as before.
Product update feature

Certificate searches accept hostnames

  • Certificate searches, single and bulk, now accept a hostname such as api.example.com as well as a registered domain, and return the certificates issued for that name and the names under it. A hostname used to be rejected as an invalid domain.
Product update fix

Platform domains such as netlify.app are accepted in domain checks

  • Domains such as netlify.app, vercel.app, pages.dev, github.io and cloudfront.net are registered domains in their own right, but WHOIS, reputation and other domain checks rejected them as an invalid domain because websites are also hosted under them. They are now accepted and checked like any other domain. Sites hosted under them, such as yoursite.netlify.app, are handled as before.
Product update feature

Instant confirmation in support

  • When you open a support ticket, the DomScan AI Assistant confirms right away that your message arrived and restates what you asked, so you know it is being handled. It is clearly marked as an automatic reply, and a person from our team still answers in the same conversation.
  • If you write again after a quiet spell, you get the same quick confirmation. It never replaces a human answer and does not change the status of your ticket.
Product update fix

Quieter watchlist alerts

  • Adding a domain to your watchlist no longer sends a status change email, or charges credits for one, when its first check finds it registered. You still get an alert right away if it is available or close to expiry.
  • The "Manage notification settings" link in alert emails now opens your alert settings, where you can switch each alert type and email alerts on or off.
  • Alert emails no longer show an empty days remaining value when the registry does not publish an expiry date.
Product update improvement

A richer support chat

  • Support messages now show formatting as you type: bold, italics, links, lists, quotes and code, from the toolbar, keyboard shortcuts or Markdown. Text pasted from a web page or document keeps its formatting, and the message box grows as you write.
  • Paste a screenshot or drag files onto the message box to attach them, now also from the chat button on every page. A message you have not sent yet is kept as a draft in your browser.
  • Every message and code block has a Copy button, so you can paste a conversation into your AI assistant as Markdown.
  • A ticket now closes on its own 72 hours after our reply if you have not answered. You can reopen it at any time to continue the conversation.
Product update feature

Send feedback from your AI agent

  • The new send_feedback MCP tool and POST /v1/feedback let you or your AI agent report a bug, wrong data or a missing feature, or tell us what works well, without leaving your workflow. Each message reaches the team right away. Sending feedback is free, and each account can send up to 10 messages per hour.
Product update feature

Website crawls, cleaner page content and document reading

  • The new Crawl API starts from one URL and returns up to 200 pages of a website as Markdown, text or HTML. It follows links on the same site up to the depth you set, can add pages from the sitemap, keeps or skips paths with patterns such as /blog/**, respects robots.txt and can notify your webhook when it finishes. The full page budget is held when the crawl starts, and pages it does not fetch are refunded when it ends.
  • The Scrape API can now keep only the main content of a page, keep or remove parts with CSS selectors, return LLM-ready text (Markdown without images or inline link targets, with links numbered at the end) and list every link on the page.
  • Scrape requests and crawls now read PDF, Word (DOCX), Excel (XLSX) and CSV files and return their text as Markdown or plain text, at the same price as a page.
Product update feature

High-volume monthly plans and aligned currency prices

  • Five new monthly plans cover larger workloads: Scale 1M, Scale 3M, Scale 10M, Scale 25M and Scale 50M, with 1 million to 50 million credits per billing period. They follow the same rules as the other monthly plans, and the price per credit goes down slightly as the volume grows.
  • Prices in euros, pounds and yen now follow the US dollar price, so monthly plans, credit packs and custom amounts cost about the same in every currency. Some prices outside US dollars go up slightly as a result.
  • If you already have a monthly plan, you keep your current price for as long as you stay subscribed. Credits you have already bought are not affected.
Product update improvement

New Enterprise page and a clearer main menu

  • A new Enterprise page explains volume pricing, higher limits, team workspaces and direct support, with a Talk to sales button that opens an email to our team.
  • The Products, Developers and Resources menus are regrouped so each section says plainly what it covers, and the mobile menu now opens as a short list you can expand.
  • Pricing and account copy is easier to read: free accounts get 1,000 credits every month, and free credits refill on the 1st of each month.
Product update security

Security hardening for billing, sign-in and scraping

  • API paths that end in a slash, such as /v1/tech/bulk/, now follow exactly the same billing, refund and bulk limit rules as the same path without the slash.
  • Sign-in now rejects requests sent from other websites on every spelling of its address, so another site cannot sign you into an account that is not yours.
  • When /v1/scrape or /v1/screenshot cannot send a request that carries your own headers or cookies through its usual secure route, the call now fails and is refunded instead of being sent another way.
Product update feature

Scrape and screenshot pages behind a login

  • /v1/scrape and /v1/screenshot accept your own request headers and cookies, such as an Authorization header or a session cookie, so you can fetch or capture your own pages that need a login or a preview token. They go only to the site you request, never to other sites the page loads or redirects to, are never stored, logged or returned, and cost nothing extra.
Product update feature

Faster page changes and an installable app

  • Moving between pages on the website is now faster and smoother: supported browsers prepare the next page when you point at a link and fade between pages instead of flashing a blank screen. You can also install DomScan as an app on your computer or phone, and if your connection drops you see a clear offline page instead of a browser error.
Product update feature

Logo, brand and company lookup APIs

  • New logo image API: /v1/logo/example.com returns the company logo as a PNG you can use directly in an img tag, with size, retina, greyscale, light or dark theme and an optional generated initials fallback that is always labelled. A wide logo is available with variant=wide. Publishable keys limited to your own websites keep the URL safe in browser code. Each request costs 1 credit, and you may store and serve the returned logos from your own servers.
  • New brand data API: /v1/brand returns a company name, description, social profiles, square and wide logos and brand colours from the logo, each with its source. Look up by domain, stock ticker, ISIN or company name. Watchlist alerts can now notify you when a brand changes its logo, colours, name or social profiles.
  • New company resolver API: /v1/company/resolve finds a company website from a stock ticker, an ISIN or a company name, and lists every candidate when the answer is ambiguous instead of guessing.
Product update fix

Failed email authentication lookups now report unknown

  • When /v1/email/verify cannot get an answer for a domain's SPF, DMARC, MTA-STS or TLS-RPT record, it no longer reports that record as missing. A failed SPF or DMARC lookup makes domain authentication not_checked, and each failed lookup is listed as an issue such as dmarc_lookup_failed.
Product update improvement

Faster repeat WHOIS lookups

  • Repeat /v1/whois lookups of registered domains answered from traditional WHOIS are now served from a 30-minute cache, like RDAP answers, with meta.cache set to hit. A repeat lookup that took several seconds now returns in well under a second.
Product update feature

Six more platforms in the social username checker

  • The social username checker now covers Keybase, Codeforces, Gitee, Lemmy (lemmy.world), Farcaster usernames and Open Collective.
Product update feature

Avatar API

  • New /v1/avatar endpoint: send an email address, a username or a domain and get the best verified profile picture or logo, where it came from, and an unknown result when no verified image exists. Unknown results are not charged. Social profile checks now also return an avatar_url when a profile picture is found.
Product update feature

Interactive domain card in MCP clients

  • In MCP clients that support interactive apps, the domain_overview tool now shows a visual card with registration, DNS, website, email authentication and reputation results. From the card you can run a TLS grade or email authentication check, or look up another domain, and each button shows its credit cost. Other clients get the same text results as before.
Product update feature

MCP server supports the 2026-07-28 protocol

  • The hosted MCP server now accepts the 2026-07-28 protocol revision, including server discovery and stateless requests, alongside the 2024-11-05, 2025-03-26 and 2025-06-18 versions. Existing clients keep working without changes.
Product update fix

Fewer rate-limit errors for page rendering checks

  • When your account already has two page rendering checks running, such as screenshots, accessibility audits or cookie scans, a new request now waits up to 10 seconds for one of them to finish instead of failing straight away with HTTP 429. A 429 response with Retry-After is returned only if no check finishes within that time.
Product update Breaking

Monthly plans and updated credit packs

  • Optional monthly plans are available in Starter (25,000 credits), Pro (100,000 credits), and Scale (500,000 credits). A paid plan replaces the free allowance while active. Unused monthly-plan credits expire at the end of each billing period and do not roll over.
  • The free allowance is 1,000 credits per UTC calendar month. It resets at 00:00 UTC on the first day of the month. Unused free credits expire then and do not roll over.
  • One-time packs are available in 10,000, 50,000, 250,000, and 1,000,000 credit sizes. Purchased pack credits do not expire, and existing pack balances remain available.
Product update fix

Auto-recharge now tops up your balance

  • With auto-recharge on, your saved card is now charged for the pack you chose within about a minute of your balance falling below your threshold, and the credits are added straight away. Before this fix the setting was saved, but no recharge took place.
  • You get an email when a recharge succeeds, and another if your bank declines it or asks you to confirm it. A failed recharge is tried again after four hours, with at most three attempts in 24 hours. Purchase and auto-recharge emails now use the language set in your email preferences.
Product update security

Request validation and network security maintenance

  • Updated the libraries used for request validation and outbound HTTP requests to include published security fixes. Existing valid API requests keep the same inputs, results and credit pricing.
Product update security

Sign-in security, MCP credits and check limits

  • Expired sign-in links and sessions are now rejected consistently. Sign-in return links stay within DomScan, and account changes that revoke MCP access also prevent pending authorization codes from restoring it.
  • MCP calls now calculate credits from the request that actually runs, including its mode and depth options. Charges and paid-only access checks follow the same rules as the HTTP API.
  • Network checks now limit oversized responses, recursive DNS work and stalled scans. Incomplete SPF and DNS zone-transfer checks are reported as unknown, while confirmed SPF failures remain failures. The email deliverability recipe rejects invalid DKIM selectors or more than 50 unique selectors before checks start.
  • Support uploads now enforce the five-file limit per message across simultaneous uploads and a 250 MiB attachment quota per account. Each file counts as at least 1 MiB toward that quota.
Product update fix

Faster availability checks for .es domains

  • Availability checks for .es domains now answer in a few seconds instead of about 30 seconds. Registered names are still reported as registered, and names without registration evidence stay unknown instead of being reported as available. Country-code domains whose registry lookup is inconclusive no longer repeat that lookup, which roughly halves their longest wait.
Product update feature

Richer link previews, bot-challenge detection and Web Vitals

  • URL intelligence now returns the author, publisher, published and modified dates, RSS and Atom feeds, the oEmbed URL, and video and audio assets. Titles, descriptions and preview images are read from more tag variants, so pages that declare Open Graph tags with name instead of property keep their preview.
  • Website identity assets rank icons by declared size, include web app manifest icons, and mark a logo as verified only when it returns a real image, not an HTML error page.
  • Page checks recognize challenge and block pages from more bot-protection services, including DataDome, AWS WAF, Imperva, Akamai, PerimeterX, Kasada and Anubis, and report those results as unknown instead of reading them as page content. Technology detection adds 8 bot-protection and CAPTCHA providers.
  • Pages served in encodings other than UTF-8, such as Windows-1252 or Shift_JIS, are now decoded correctly, so accented and non-Latin text is no longer garbled.
  • Page weight now reports lab Core Web Vitals (LCP, CLS and TBT) with ratings. Screenshots finish loading sooner and hide cookie banners by default; set hide_cookie_banners=false to capture the page as served.
Product update feature

Changelog RSS feed

  • The changelog now has an RSS feed in every supported language, so you can follow new features, fixes and breaking changes in any feed reader. Each item links to its entry on this page.
Product update fix

Pricing lookups handle unavailable sources

  • Single-TLD pricing, TLD price lists and domain price comparisons now report unavailable sources without failing the request. When no selected source can provide data, no prices or recommendations are returned and request credits are refunded.
Product update fix

Bulk pricing handles unavailable sources

  • Bulk price requests now return an explicit unavailable status and no prices when every selected registrar source is temporarily unavailable. These requests are refunded, and stale prices are never returned.
Product update improvement

Status page measures uptime only

  • The status page now reports uptime only. A product family shows as an outage only when fewer than half of its requests in the last 15 minutes succeed, and response times no longer appear or affect status.
Product update fix

Social username checks respect evidence freshness

  • If a new social username check fails, evidence older than that platform’s freshness limit no longer marks the username as taken. Expired evidence leaves the result unknown; current exact profile evidence and fresh cached results are unchanged.
Product update fix

More reliable domain price comparisons

  • Standard domain price lists now exclude alternative namespaces and entries that do not establish a usable price, so they are not shown as free domains.
Product update fix

More reliable Facebook and itch.io profile checks

  • Facebook checks no longer treat generic or malformed picture responses or redirects to help and product pages as proof of an account. Exact profile evidence is still required; inconclusive responses stay unknown.
  • itch.io checks now recognize an account whose creator link points to the homepage when exact account metadata confirms the requested profile. Generic pages and mismatched profiles remain unknown.
Product update feature

More WHOIS coverage for country domains

  • WHOIS lookups now recognize registered and unregistered domains under .ga, .jo, .sx, .gt and .com.gt. Blocked, timed-out and ambiguous responses remain unknown.
Product update feature

Business verification, sanctions screening, security rating and website compliance

  • Validate an IBAN for any IBAN country, a BIC/SWIFT code and a US routing number with POST /v1/bank/validate (1 credit). A valid IBAN is split into bank code, branch code and account number. The check runs offline and bank details are not kept in request logs.
  • Check VAT numbers with GET /v1/vat/validate (1 credit): EU and Northern Ireland numbers live with the EU VAT register and Norwegian numbers with the Norwegian business register, with the registered name and address where the country discloses them. UK, Swiss and Australian numbers are checked for format and check digits. When a register does not answer, the result is unknown and not charged.
  • Validate Spanish DNI, NIE and NIF/CIF numbers with GET /v1/national-id/validate (1 credit), with the type of company and the correct control character when it is wrong.
  • Look up and verify a US healthcare provider by NPI with GET /v1/npi, comparing a name, state and specialty with the record, or search providers by name with GET /v1/npi/search (1 credit each).
  • Screen a person or company name against the US OFAC SDN and consolidated, UN, EU and UK sanctions lists with POST /v1/sanctions/screen (2 credits). Lists are refreshed daily, and no_match is returned only when every list is current.
  • Grade a domain's security from A to F with GET /v1/security-rating (5 credits), from its certificate, security headers, email authentication, DNS, blocklist reputation and security contact. Areas that cannot be checked are left out of the score.
  • Find a website's privacy policy, terms, cookie policy, imprint, privacy choices link, consent manager and trackers with GET /v1/legal-compliance (2 credits, 6 with render=true). Every new check also has an interactive tool.
Product update fix

More reliable WHOIS availability results

  • WHOIS lookups no longer mistake a registry comment about an available contact form for an available domain. Explicit query limits remain unknown, including when a response also contains domain data.
  • WHOIS lookups no longer treat a registry’s general rate-limit policy as a rejected query. Only an explicit limit response is reported as unknown.
  • RDAP checks now respect retry delays after 403 or 429 responses. Unregistered names in confirmed closed brand extensions, including .microsoft, .google and .dhl, remain unavailable for public registration, keeping registration status separate from availability.
  • WHOIS checks now recognize active .ma records as registered and an exact “Domain not found” reply on .sh as absent. Mixed, incomplete, or error replies remain unknown or unavailable and do not confirm registration or absence.
  • WHOIS checks now recognize current registry replies for .ki, .bi, .ci, .ax, and .ls, and retrieve records more reliably for .cr and .sa. Conflicting, incomplete, malformed, denied, or throttled replies remain unconfirmed.
  • WHOIS checks now recognize current registry replies for .gh, .do, .vu, .ar, and .ws. A missing contact record no longer makes a registered .mq domain appear available, and denied or throttled replies remain unconfirmed.
  • WHOIS checks now recognize current registry responses for .bf, .td, .kn, .mr, .mc, and .ws, with lookup support for .tm. Queries for Chinese IDN domains under .中国 and .中國 now use the Unicode domain format required by the registry. Incomplete, denied, or throttled replies remain unconfirmed.
Product update fix

More accurate email, blocklist, lookalike and hosting results

  • Email compliance reports SPF, DKIM or DMARC as unknown when its lookup fails, instead of failing the check and advising you to publish a record. Unknown checks are left out of the score, and a report where all three lookups fail is refunded.
  • Email checks, email verification, DNS security, reputation, domain health and the email deliverability and phishing investigation recipes report a blocklist that could not answer as unknown instead of clean.
  • Domain similarity decodes internationalized names and reports a lookalike that uses characters from another script, such as a Cyrillic а in apple.com, as a critical homograph.
  • Hosting detection uses the most specific matching network range, so a provider inside a broad cloud block is named correctly. Email forwarding services such as addy.io and SimpleLogin are no longer flagged as disposable.
  • Company lookup no longer keeps a result from a failed homepage or mail server lookup for a full day, and the Substack handle check now recognizes the platform's not-found page.
  • Watchlist history, webhook deliveries and expiring domains handle invalid limit and days values instead of failing, the watchlist includes every monitored domain, and 30-day usage totals and comparisons now cover exactly 30 days.
Product update fix

More accurate blocklist, email, DNS and monitoring results

  • Blocklist checks report a list that refused the query or could not be reached as unknown instead of clean, no longer count refusal codes as listings, and name listing categories correctly. Each list now has a status, and the result counts the lists that could not answer.
  • Email verification reports an address as unknown and refunds the check when the mail server lookup fails, instead of rejecting it as a domain with no mail servers.
  • IP lookups no longer flag a reverse DNS mismatch when the forward lookup fails, and domain change monitoring no longer reports DNS or email records as removed when a lookup fails.
  • Page checks apply an X-Robots-Tag rule scoped to one crawler (such as otherbot: noindex) only to that crawler, scraped text keeps table cells and list items apart, and name checks report a handle that breaks a platform's rules as invalid instead of unknown.
  • Domain lifecycle results read pendingRestore as expiring, pendingCreate as pending and serverHold as reserved. A brand monitor added again takes a fresh baseline, so earlier lookalikes are not alerted as new, and scrape jobs keep refunds owed for failed items until they are paid.
  • Fixed translation errors in several languages, including notification channel names, domain status codes in glossary articles and Monitor page labels left partly in English.
Product update fix

More dependable domain monitoring alerts

  • Check now on a monitored domain sends the same availability, status and expiry alerts as a scheduled check. Before, it saved the new state without alerting, so a change it found first was never alerted.
  • A temporary lookup failure no longer marks a monitored domain as unknown or clears its expiry date, so it no longer sends a status change alert and a repeat expiry alert once lookups recover.
  • The authentication section of the API docs now says correctly in every language that requests need an API key, and links to the dashboard where you manage it.
Product update fix

Fairer credit charges for MCP, batches and query options

  • Page scraping through the MCP server is no longer charged twice, and accounts with purchased credits can use every scrape mode there.
  • Credit charges now follow the options a request actually runs with: a repeated query parameter is priced by its first value, modes such as mode=DEEP are matched regardless of case, and true or false values such as TRUE, yes or 0 are priced the same way the endpoint reads them. Domain suggestions and typo checks accept the same true and false values as other endpoints.
  • Batch jobs now refund an item whose result could not be confirmed and return the unused credits of an item that was only partly delivered, as single requests already did.
Product update fix

More reliable page, company and lookup checks

  • Technology scans return page titles and descriptions with HTML entities decoded, page checks no longer fail on deeply nested structured data, ads.txt checks report a bot challenge page as blocked instead of invalid, and sitemap audits read Sitemap lines from a robots.txt served as HTML.
  • Company lookups keep hyphenated names such as Coca-Cola and no longer report share or hashtag links as official social profiles.
  • Steam handle checks report a temporary Steam error as unknown instead of no account found, RDAP lookups reject malformed IP ranges and AS numbers, and invalid unsubscribe links or usage periods return a clear error instead of failing.
Product update fix

More accurate reports, recipes and comparisons

  • The domain report now returns the reputation score, blacklist status, recommendations and subdomain count, marks the DNS or subdomain section as failed when its lookups fail, and refunds a report where no section could be completed.
  • The Brand Launch recipe now reports the real brand name score and keeps an unconfirmed registration status or unchecked social handles pending instead of passing them, and the Portfolio Audit no longer scores an incomplete health check as 0.
  • Domain comparisons no longer describe a domain with unknown availability as registered, and now include registration and expiry dates.
  • Availability checks for Unicode extensions such as .рф now query the registry directly, and domain age in years counts whole years up to the registration anniversary.
Product update fix

More accurate DNS, hosting, typo and page checks

  • DNS lookups no longer label an alias (CNAME) answer as an A record, CDN detection no longer reports Amazon CloudFront and other caches as Fastly, and parking detection no longer flags sites that only link to domains such as jordan.com.
  • Typo checks now include multi-letter look-alikes such as rn for m and vv for w, and MAC lookups classify device types by whole vendor names.
  • Page checks treat robots "none" as noindex, no longer fail on unusual character codes, count words correctly in Hindi, Tamil and other scripts with combining marks, flag content as needing JavaScript only when rendering adds it, and treat Disallow: /* as blocking AI crawlers.
Product update fix

Reliability fixes for sign-in, tools and checks

  • Sign-in, sign-up, the workspace monitor and 24 tool pages work again in French, Italian and Turkish, where some translated text stopped the page from loading.
  • DNS and email authentication checks read DKIM keys published in several parts, read the DMARC policy correctly when sp= comes first, count SPF lookups for every mechanism and report a failed DNS lookup as unavailable instead of a missing record.
  • The Suggestions tool now uses the extension and availability option you choose, and the domainers page shows the correct credit cost for each API.
  • Typo, suggestion and name checks handle invalid limits and repeated inputs, phone validation keeps written extensions, and vulnerability, threat and MAC lookups return more accurate results.
Product update improvement

Telegram handle checks show when no account uses a name

  • Telegram handle checks now report a name with no Telegram account as claimability_unknown, shown as No account found, instead of rate_limited. Telegram shows the same page for unused names and when it limits requests, so a name is reported this way only when a known Telegram account loads correctly just before and just after it. Telegram offers no public way to confirm that a name can be registered, so it is never reported as available.
Product update fix

Clearer LinkedIn, Reddit, Telegram and Threads handle checks

  • LinkedIn checks no longer fail on company pages served from country-specific LinkedIn addresses, and a page that was renamed is reported as taken.
  • Reddit checks give a definite answer more often, and suspended Reddit accounts are reported as taken. Telegram reports short and system usernames as reserved, and reports a temporary Telegram limit as rate_limited instead of an error. Threads checks are faster.
  • Bitbucket, Vimeo, Linktree, Tumblr, Behance, Gumroad, itch.io, Letterboxd, Patreon, Steam and Hacker News no longer report a name as available only because no public profile was found. Those names are reported as claimability_unknown, shown as No account found.
  • Buy Me a Coffee and Substack now confirm availability with the username check each site runs before sign-up, and report names the site refuses as reserved.
Product update feature

New Name Availability API

  • New Name Availability API (/v1/name-check) checks a name as domains across up to 20 extensions, as a handle on 20 social and developer platforms and as a package in npm, PyPI, crates.io, RubyGems, NuGet, Packagist and Homebrew, with a verdict and score. It has a free Name Checker tool and documentation.
Product update feature

New Robots.txt Tester API

  • New Robots.txt Tester API (POST /v1/robots/test) checks up to 100 URLs against up to 10 crawlers in one request, using a robots.txt you paste or the live file, with the deciding rule, its line and syntax issues. It has a free tool page and documentation.
Product update feature

Seven new website analysis APIs

  • New Site Audit API (/v1/site-audit) crawls up to 50 pages, follows robots.txt and reports broken internal links, redirects, duplicate titles and content, noindex and thin pages and on-page issues.
  • New Screenshot API (/v1/screenshot) captures any page as PNG, JPEG, WebP or PDF on desktop or mobile, visible area or full page, in JSON or as the raw file.
  • New Accessibility Audit API (/v1/accessibility) runs automated WCAG checks and returns violations by impact, affected elements and a score.
  • New Cookie Scanner API (/v1/cookie-scan) lists cookies, trackers, third parties and the consent manager a page loads before consent, without collecting cookie values.
  • New Page Weight API (/v1/page-weight) measures bytes and requests by type, largest files, third-party weight, render-blocking resources and load timings.
  • New ads.txt API (/v1/ads-txt) validates ads.txt and app-ads.txt and confirms sellers against sellers.json.
  • New Duplicate Content API (/v1/duplicate-content) compares up to 10 pages for near-duplicate content and repeated titles, meta descriptions and H1s. Each new API has a free tool page and documentation.
Product update feature

Six new on-page SEO APIs

  • New On-page SEO Audit API (/v1/onpage) checks titles, meta tags, canonicals, robots directives, headings, content, links, images and structured data with 38 checks and a 0-100 score. Add render=true to audit the page after JavaScript runs.
  • New JavaScript SEO API (/v1/onpage/render-diff) compares the raw and rendered HTML of a page and lists the SEO signals that only appear or change after JavaScript runs.
  • New Structured Data API (/v1/structured-data) extracts JSON-LD, Microdata and RDFa and validates 26 common schema.org types, with errors and warnings for each property.
  • New Keyword Density API (/v1/keyword-density) returns the top one, two and three word phrases with density and checks where target keywords appear.
  • New Page Links API (/v1/links) lists every link with anchor text and rel values and, with check=true, finds broken links among up to 25 targets.
  • New Hreflang API (/v1/hreflang) validates hreflang codes, x-default and self references, and confirms return links on up to 20 alternate pages. Each API has a free tool page, documentation and an MCP tool.
Product update fix

More accurate Facebook, Instagram and TikTok handle checks

  • Facebook checks now return a clear answer for almost every handle and respond much faster. Handles with no Facebook account are reported as claimability_unknown, shown as No account found, instead of an error, and Facebook accepts handles from 1 character long.
  • Instagram no longer labels private accounts as reserved. A handle that Instagram refuses at sign-up is reported as taken, and reserved is used only for names that break Instagram username rules. Instagram and Threads checks are also faster.
  • TikTok private and restricted accounts are reported as taken instead of an error.
Product update improvement

Nine more social platforms and stricter availability answers

  • New platforms: Discord, Roblox, Kick, Chess.com, Minecraft, Mastodon (mastodon.social), Medium, npm and Lichess. Discord, Roblox, Kick and Chess.com use the username check each platform runs before sign-up, so they can confirm that a name is free.
  • Instagram, X, Snapchat and Twitch now confirm availability with the username check those platforms run before sign-up. Names they refuse, such as reserved or banned names, are reported as taken or reserved instead of available.
  • Fewer handles are wrongly reported as available. TikTok, YouTube, Pinterest, SoundCloud, Hugging Face, Docker Hub and LinkedIn now report a name with no account as claimability_unknown, shown as No account found, because they offer no public way to confirm that it can be registered. DEV names used by podcasts are reported as taken.
  • Threads reports a handle as taken when the matching Instagram account holds it. Telegram reports handles sold through its username marketplace as taken, and handles listed there for sale or auction as reserved.
  • LinkedIn checks now recognise school and showcase pages, which share names with company pages.
Product update fix

More accurate and more complete social username checks

  • Fewer handles are wrongly reported as available. Private Dribbble profiles, suspended or banned Twitch accounts, private GitLab groups and hidden users, Hacker News accounts that have never posted, and Hashnode and RubyGems usernames in a different letter case are now reported as taken. Bluesky names that Bluesky keeps back are reported as reserved.
  • When a platform confirms that no account uses a handle but does not confirm that it can be registered, the result now says so: available stays null, reason is claimability_unknown and classification.status is absent. GitHub, Dribbble, Hashnode, RubyGems and Snapchat use this result, and the Social Handle Checker shows it as No account found. GitHub could not check these handles before.
  • Bluesky now checks plain names such as brand as brand.bsky.social instead of rejecting them as invalid.
  • More checks give a definite answer. Deactivated Bitbucket workspaces, hidden Tumblr blogs, private Vimeo members, unverified Linktree profiles, suspended X accounts and removed Patreon creators are now reported as taken instead of unknown, and Pinterest, Facebook, Patreon, itch.io, Behance and Hacker News checks answer faster.
  • When a platform does not answer clearly, the check is retried once within the request time limit. If it still has no answer, a handle confirmed as taken in the last 30 days is reported as taken, with evidence.source set to stale_cache and the age of that evidence in cache_age_s. Earlier available results are never reused this way.
  • If a platform starts reporting well-known accounts as available, DomScan stops reporting handles as available on that platform until its answers are correct again. Those results are unknown, with evidence.source set to canary_quarantine.
Product update improvement

One credit per pair across domain pricing

  • Each unique TLD and selected registrar pair actually checked costs 1 credit across GET /v1/prices, GET /v1/prices/tld/:tld, POST /v1/prices/bulk for up to 50 unique TLDs, and GET /v1/prices/compare. GET /v1/prices requests for more than 5 TLDs also cost 1 credit per pair. The catalog remains free when tlds is omitted.
  • In /v1/prices/compare, a standard row and a live exact-domain quote for the same pair are billed once together. Duplicate TLDs and registrar IDs are counted once, and registrar filters reduce planned and actual checks and credits charged.
  • A failed or unknown exact quote is refunded only when no standard price row for that pair is returned.
  • When a daily source refresh fails quality checks, its last accepted prices are retained, and the source stays out of recommendations until a valid refresh succeeds.
  • Standard and bulk price lookups now accept supported compound extensions from the current pricing catalog, even when they are absent from the domain-checking list.
Product update fix

More reliable Telegram username checks

  • Telegram checks now return unknown when a contact page or missing public page cannot confirm username availability. Exact public channel and bot matches still identify existing profiles.
Product update security

Safer AI app connections, team invitations and pages

  • Connections from AI apps through MCP now expire one year after you approve them, and an app can revoke its own connection at any time. Existing connections keep working for at least 30 more days.
  • Team invitation emails no longer put the account name in the subject or heading and always show who sent the invitation. Account names can no longer contain links, web addresses or email addresses.
  • Every page now runs only the scripts DomScan put there, so injected code is blocked by the browser even if it reaches a page.
  • When our abuse protection blocks a new sign-up, the sign-in form now says the email was not sent instead of appearing to succeed.
Product update improvement

Five checks now have their own product pages

  • The robots.txt, XML sitemap audit, security headers, security.txt and IDN homograph checks now appear as their own products in the product menu, the API catalog and their suite pages, each linking to its own API page.
  • Each of the five checks also has its own page in the documentation navigation, so you can go straight to its parameters and examples.
Product update security

Security hardening for sign-in and pages

  • Google sign-in now requires a verified Google email, never replaces a Google account already linked to your DomScan account, and rejects sign-in requests sent from other sites.
  • Pages and tools that show data from domains, registries and certificates now escape it everywhere, and the screen for connecting an AI app shows the exact address the authorization is sent to.
Product update improvement

Better on phones, and four tools fixed

  • The site, free tools, documentation and dashboard were reviewed on phones: comparison and cost tables stack into readable rows, buttons and links are easier to tap, and form fields no longer zoom the page on iPhone.
  • The tech stack, agent readiness, watchlist and email verification tools work again after a script error stopped their results, and the DKIM checker now lists the selectors it finds.
Product update improvement

Interactive API docs: Try it for POST, your key in code samples and full search

  • Try it now runs GET and POST examples from the docs with your signed-in account, and shows the credit cost before you choose to run the request.
  • Paste your API key once to fill it into every code sample on the docs pages and into copied code. The key stays in your browser tab, and Forget key removes it.
  • Every endpoint now has cURL, Node.js, Python, Go and Ruby examples, and your chosen language is remembered across docs pages, including product docs.
  • Press Cmd+K or Ctrl+K to search section titles, headings, endpoint paths and parameter names across the whole API documentation.
  • Docs pages now show when their content last changed, and every docs page asks whether it was helpful, with an optional comment.
Product update feature

AI-ready API documentation

  • Every docs page now has a Markdown version at the same address with .md added, and /llms-full.txt holds the complete documentation in one file for AI assistants.
  • A menu next to each docs page title copies the page as Markdown, shows the Markdown version, or opens the page in ChatGPT, Claude, Perplexity or Cursor.
  • Ask AI (Ctrl+I or Cmd+I) sends your question to ChatGPT or Claude together with links to the docs, so answers are based on the current documentation. DomScan does not see your question.
Product update security

Rate limits count by verified identity

  • Rate limits on public endpoints now always count by client address unless a valid API key is used. An X-API-Key or Authorization header that is not verified no longer changes which limit applies.
  • Requests made with a valid API key or a signed-in session count toward your account's limit, shared across all of its keys. The X-RateLimit-Policy header reports this as scope=account.
Product update feature

One-click MCP install and a guide for AI agents

  • The MCP page and the API docs now have Add to Cursor and Add to VS Code buttons, plus copyable Claude Code and Codex commands, so you can connect DomScan without editing a config file.
  • A new guide at /docs/ai-agents explains when to use MCP or the REST API, covers setup for Claude Code, Cursor, VS Code, Codex, ChatGPT, Claude and Windsurf, and includes an AGENTS.md snippet and ready-made prompts.
  • The docs sidebar now links to the changelog, system status, the API playground and the public agent guide.
Product update feature

Public system status page

  • A new status page at /status shows whether each API product family is operational, degraded or in an outage, based on requests from the last 15 minutes.
  • Each product family shows its current p95 response time and 90 days of daily uptime.
  • Ongoing incidents and incidents resolved in the last 30 days are listed with timestamps and plain-language updates.
Product update improvement

A shorter MCP tool list

  • The MCP server now lists 98 tools instead of 153, so agents load about 20% less tool text. Single and bulk checks share one tool: send a list such as domains instead of domain to run the bulk version.
  • Related operations such as SSL checks, typosquatting analysis, SPF, DMARC and DKIM checks, job status and free reference data now share one tool with an action argument. Each tool description lists the credit cost of every action, and credits are charged exactly as before.
  • Old tool names keep working until at least 2027-10-10. Tools that delete, cancel or remove something stay separate. The full list of old and new names is on the MCP page and at /mcp/tool-mapping.json.
Product update feature

Optional snake_case keys and a versioning policy

  • Add naming=snake, or send the DomScan-Naming: snake header, to receive every camelCase response key in snake_case, for example registrar_name instead of registrarName. Values, error responses and credit costs are unchanged, and MCP tools accept the same naming argument.
  • A new versioning policy explains which changes ship without notice and commits to at least 12 months of notice before any breaking change.
  • Requests that use a deprecated alias, such as skip_cache, prefer_cache, refresh, offset or a numeric certificates cursor, now receive Deprecation, Sunset and Link headers. These aliases keep working until at least October 10, 2027.
Product update fix

Fewer false brand monitoring alerts

  • Brand monitoring now reports a lookalike as a new threat only when a registration lookup confirms it is registered, the same rule the lookalike watchlist alerts use. Uncertain, blocked or timed-out checks no longer count as threats and are checked again on the next scan.
  • A lookalike already recorded for your brand stays in your baseline and is reported as resolved only when a lookup confirms it is no longer registered.
Product update feature

Safe retries and separate state for each marketplace subscriber

  • Marketplace subscribers can send an Idempotency-Key header on supported POST requests. Retrying with the same key within 24 hours returns the original response. Keys, pagination cursors and rate limits are kept separate for each identified subscriber.
  • Marketplace responses include the X-RateLimit and X-Data-Freshness headers and no X-Credits headers, because marketplace plans are billed per request. dry_run=true returns 400 DRY_RUN_NOT_AVAILABLE for marketplace subscribers.
Product update feature

Certificate, price, DNS and lookalike alerts

  • Subscribe watched items to new alert events with /v1/watchlist/alerts: ssl.expiring, ssl.expired and ssl.changed for any hostname, price.dropped for a TLD price, dns.changed for the records of any hostname, and typosquat.detected for new lookalikes of a brand domain.
  • Each subscription is opt in per item and per event, with a certificate expiry threshold of 30, 14, 7 or 1 days, a price drop percentage or target price, and the DNS record types to watch.
  • Only exact evidence triggers an alert. Failed or timed-out checks change nothing, and certificate and DNS changes must be seen on two consecutive checks before they are sent.
  • Checks are free. Each alert delivered to your signed webhook with a 2xx response costs 2 credits, the same as other monitoring alerts, and failed deliveries are refunded.
Product update feature

Freshness control and cursor pagination

  • Endpoints that can answer from recently checked data, such as availability, subdomain, certificate, technology and website checks, accept max_age in seconds. Older data is checked again, max_age=0 always checks fresh, and responses report the age of the data in cache_age_s and the X-Cache-Age header. Credit costs are unchanged.
  • WHOIS and DNS history, subdomains, certificates, watchlists, brand monitors and the disposable email domain list accept limit and cursor and return has_more and next_cursor. Requests without limit return the same results as before, and each page costs the same as one request.
  • skip_cache, prefer_cache, refresh and offset keep working as deprecated aliases.
Product update feature

Structured MCP results and tool hints

  • MCP clients on protocol version 2025-06-18 or later now receive structuredContent with the same JSON object as the text result, including results narrowed with fields or compact. Results in plain text or CSV stay text only.
  • Every tool now has a title and hints that say whether it only reads data, changes saved items, deletes or cancels something, or contacts the internet.
  • Tool descriptions no longer repeat the API path, which keeps the tool list shorter. Tool names, inputs, credit costs and text results stay the same, and errors are still returned with isError and the standard error object.
Product update feature

Field selection and compact responses

  • GET and POST API requests accept an optional fields parameter with comma-separated dot paths, such as fields=domain,classification.status, and return only those fields. Paths that match nothing are listed in the X-Fields-Ignored header.
  • compact=true removes serving metadata, such as timings and empty warning lists, without removing data fields. Both parameters also work on MCP tool calls, never change the credit cost and leave error responses unchanged.
Product update feature

One API for every async job

  • GET /v1/jobs lists your API batches, domain discovery, technology scan and scrape jobs together, newest first, with limit and cursor pagination. Every job has the same shape for status, progress, credits and links, and its results page through GET /v1/jobs/:job_id/results.
  • POST /v1/jobs/:job_id/cancel cancels API batch, domain discovery and technology scan jobs with one call, and unstarted items are refunded. Listing, reading and cancelling jobs is free, and the existing job endpoints keep working unchanged.
  • Job creation endpoints accept notify_webhook. When the job finishes, your signed webhook endpoints receive one free job.completed, job.failed or job.cancelled event.
Product update feature

Cost estimates, safe retries and credit headers

  • Every authenticated API response, including errors, now reports X-Credits-Charged, X-Credits-Remaining, X-RateLimit-Limit, X-RateLimit-Remaining and the new X-RateLimit-Reset, so you can track spending and limits from the headers alone.
  • POST /v1/estimate returns the credits a request would cost, with a breakdown and notes, without running it. Bulk, compare, recipe and pricing endpoints also accept dry_run=true. Both are free.
  • POST requests that charge credits accept an optional Idempotency-Key header. Retrying with the same key within 24 hours returns the original response without charging again.
Product update improvement

One present, absent or unknown status across presence checks

  • Availability, social handle, DNS and email authentication, security.txt, robots.txt, sitemap, security header, parking, typosquatting and SSL certificate responses now include a classification object with a status of present, absent or unknown, the evidence behind it and when it was checked. Existing fields are unchanged.
  • Unknown results always carry a reason: blocked, rate_limited, timeout, ambiguous, upstream_error or unsupported. Blocked, rate-limited, timed-out and failed checks are never reported as absent.
  • Fixed results that treated failed checks as missing: failed DNS lookups no longer report SPF, DMARC, DKIM, CAA, MTA-STS or DNSSEC as missing, unreadable homepages no longer report a domain as not parked, typosquatting checks no longer count unconfirmed names as registered, and security header recommendations are no longer built from blocked pages.
  • Scores and grades no longer treat a failed check as missing. The DNS security score and the email authentication grade leave unknown checks out, report how many in the new checks_unknown and score_confidence fields, and return null when every check is unknown. The SSL grade is null with a grade_reason instead of F when no certificate could be read, social checks report blocked instead of rate_limited when a platform refuses access, and the reputation score reports unknown parking as null instead of not parked.
Product update Breaking

New credit costs for the domain pricing API

  • Single standard price lookups keep their cost: /v1/prices/tld/:tld and /v1/prices requests for up to 5 TLDs cost 1 credit per TLD and registrar pair, and the free TLD catalog is unchanged.
  • Larger catalogue requests now cost 2 credits per TLD and registrar pair. This applies to every POST /v1/prices/bulk request and to /v1/prices requests for 6 to 20 TLDs.
  • In /v1/prices/compare, each registrar that returns a live exact-domain quote now costs 3 credits. If a live quote fails or its result is unknown, it costs 1 credit when that registrar's daily price is shown and nothing otherwise. Registrars shown from their daily price list still cost 1 credit, and checkAccounting reports liveQuoteChecks, creditsPerLiveQuote and creditsRefunded next to creditsCharged.
Product update feature

Domain price comparison covers five more providers

  • Standard registration, renewal and transfer prices now include INWX, 101domain, Rebel.com, iwantmyname and Cosmotown.
  • Sale prices, new-customer offers and dated campaigns are shown separately from regular prices. Extensions sold only for terms longer than one year are left out.
Product update fix

Correct certificate serial numbers and a documented DNS ALL lookup

  • SSL grade and chain results no longer show a certificate transparency log entry ID as the certificate serial number. The serial number is returned when it is read from the live certificate and left out otherwise.
  • The DNS lookup documentation and the OpenAPI specification now describe type=ALL, which returns every common record type in one request. They also describe fields that responses already returned, such as the remaining watchlist after a removal and the top-level totals in bulk WHOIS results.
Product update fix

Accurate DKIM key sizes and more complete API documentation

  • DKIM checks now report the real public key size, for example 2048 bits for an RSA-2048 key instead of a larger estimate based on the encoded key length. Ed25519 keys report 256 bits and are no longer flagged as too small.
  • The OpenAPI specification and SDK types now describe fields that responses already returned, such as DMARC alignment settings, SPF includes and status flags in availability results. Bulk availability checks also accept prefer_cache at the top level of the request body and now include a summary block.
Product update improvement

One consistent error format across the API

  • Every API error now returns the same JSON error object with a stable code, a readable message, its type and HTTP status, whether a retry can help, a request ID that matches the X-Request-Id header and a link to the relevant documentation.
  • Unknown API paths now return a JSON 404 error, and supported paths called with the wrong HTTP method return a 405 error that lists the allowed methods. The error codes reference now includes retry guidance.
  • Existing integrations keep working: error codes are not renamed, success responses are unchanged and fields some endpoints already returned, such as credits_remaining or purchase_url, stay in place during a compatibility period.
Product update deprecation

Single notification webhook retired for new setups

  • The single webhook in notification settings can no longer be turned on, and its URL can no longer be set or changed. Accounts that already use it keep receiving alerts as before, with the same payload and signature.
  • You can still disable or clear an existing single webhook, but it cannot be turned back on afterwards. Slack, Discord, Telegram and email notifications are unchanged.
  • Move to signed webhooks from Monitor settings or the /v1/webhooks API for timestamped signatures, automatic retries, a delivery log, more alert types and up to 10 endpoints. Each delivered alert costs 2 credits.
Product update feature

Webhook secret rotation and pause emails

  • Rotate the signing secret of an alert webhook endpoint from Monitor settings or with POST /v1/webhooks/:webhook_id/rotate-secret. Rotation is free, and the new secret is shown once.
  • For 24 hours after a rotation, each alert is signed with both the new and the previous secret in X-DomScan-Signature, so your receiver can switch without missing alerts.
  • When an endpoint is paused after repeated failures, you now get one email with the endpoint host, the last error and a link to enable it again. Enabling it resets the failure count.
Product update feature

Monitoring alerts on your own webhooks

  • Register up to 10 HTTPS endpoints from Monitor settings or the /v1/webhooks API, and choose which watchlist, domain change and brand monitoring alerts each one receives.
  • Every alert is signed with HMAC-SHA256 over a timestamp and the request body. Failed deliveries are retried with increasing delays, and an endpoint that keeps failing is paused until you enable it again.
  • Each alert delivered with a 2xx response costs 2 credits. Failed deliveries are refunded and test events are free.
Product update feature

Domain price comparison covers nine more providers

  • Standard registration, renewal and transfer prices now include OVHcloud, Gname, WordPress.com, WebNIC, NearlyFreeSpeech.NET, Hostiso, HostSailor, HostUS and VirMach.
  • First-year offers and sale prices are shown separately from regular prices. Prices published only for a multi-year term are left out instead of being converted to a yearly figure.
Product update feature

Five new APIs: robots.txt, sitemaps, security headers, security.txt and IDN

  • GET /v1/robots parses robots.txt, tests any user agent and path, and reports access for 14 AI crawlers. GET /v1/sitemaps discovers and audits XML sitemaps with URL counts, freshness and protocol issues.
  • GET /v1/headers grades HTTP security headers and cookie flags, and GET /v1/security-txt validates security.txt files against RFC 9116.
  • GET /v1/idn converts Unicode and punycode domains and detects lookalike characters. All five are available in the API, the MCP server and as free tools.
Product update fix

SSL checks no longer report unreadable certificates as expired

  • The SSL expiry check returns a new certificate_status field. When the certificate cannot be read, the status is unknown and the response no longer reports it as expired.
  • Domain reputation flags an invalid certificate only when there is certificate evidence. A site that does not answer over HTTPS gets a recommendation to check HTTPS instead.
Product update feature

Getting started checklist and faster pages

  • New accounts see a short checklist on the dashboard: create an API key, make a first request and monitor a domain. Each step completes automatically from your account activity, and the checklist can be hidden.
  • Pages load faster on repeat visits because shared styles and scripts are now downloaded once and reused across the site.
Product update improvement

Redesigned website and dashboard with light and dark themes

  • Every public page and the signed-in dashboard now support light and dark themes. DomScan follows your system setting by default, and the theme switch in the header lets you choose light, dark or system.
  • A cleaner, more readable design across the site: clearer typography, calmer layouts and consistent components on product, documentation, pricing and account pages.
  • The home page explains more directly what DomScan does, with a real request and response example next to the introduction.
Product update fix

More accurate domain and IP lookup results

  • RDAP registration lookups now reject hostnames and ordinary subdomains as invalid inputs instead of reporting a temporary outage that may prompt an unnecessary retry.
  • Taiwan domain (.tw) lookups are working again.
  • Identity and vulnerability results now mark missing webpage evidence as partial or unknown instead of clean or empty. When a result is unavailable, its credits are refunded.
  • IP lookups now reject domains that resolve only to private or reserved addresses before enrichment, with an accurate input error instead of a temporary failure.
Product update fix

More precise social username availability checks

  • A generic Facebook or Threads profile page that returns ‘not found’ no longer counts as proof that a username is available.
  • GitHub results now require the public profile to match the requested username exactly. The exact Threads check and results that already confirm a username exists remain unchanged.
Product update feature

AppSumo license activation and monthly credits

  • Connect an AppSumo license to the DomScan account you are signed into, then use the deal across supported DomScan products.
  • AppSumo tier changes and refunds update the monthly credit allowance. Unused monthly credits expire at the UTC calendar-month boundary, while separately purchased credits remain in the account.
Product update fix

More dependable domain registration results

  • Availability checks now follow current registry support for each domain suffix, avoiding WHOIS requests where that service is not offered.
  • Incomplete, contradictory, or blocked registry replies now stay unknown instead of being reported as registered or available.
Product update fix

More reliable domain checks

  • Subdomain discovery can now check certificate records when earlier checks use most of the available time.
  • Technology scans now allow a slow page request more time to finish before timing out.
  • For `.io` and `.biz` domains, if RDAP reports no registration but WHOIS is rate limited, lookup results now show DNS-only data as uncertain and refund the request credits instead of returning a server error.
  • WHOIS checks for `.io` and `.biz` now have more ways to retrieve registration evidence when a registry limits requests.
Product update fix

Certificate and subdomain results preserve uncertainty

  • Certificate searches no longer treat rate-limited or malformed source responses as empty results. Subdomain discovery reports uncertainty when no source can provide evidence.
Product update fix

Unclear WHOIS replies stay unknown

  • Generic WHOIS replies that are short or unrecognized now remain unknown instead of appearing available. Results still depend on exact, authoritative registry or RDAP evidence.
Product update fix

More reliable WHOIS checks for .mu, .africa and .sr

  • When RDAP is unavailable, availability checks for `.mu`, `.africa`, and `.sr` use registry-specific WHOIS routing. Exact authoritative replies determine results; blocked or inconclusive responses remain unknown.
Product update fix

Registration availability is clearer

  • The .apple registry is closed to public registration, so unregistered .apple names are no longer shown as taken or available.
  • A .us WHOIS response that says no record was found while disclaiming availability now remains unknown.
Product update fix

RDAP coverage now marks unmeasured health clearly

  • Coverage responses no longer report success or latency and error values when no live probe ran; those measurements are marked unmeasured.
  • Live coverage checks make one probe per distinct RDAP host, so latency and error values describe that probe rather than historical performance.
Product update fix

Clearer WHOIS availability results

  • The WHOIS lookup tool now shows an explicit Available or Taken result when registration data is limited.
  • Availability checks for `.info` domains now use a more reliable connection path.
Product update fix

Fixed `.my` and `.com.my` availability results

  • Availability searches for `.my` and `.com.my` domains now correctly distinguish available domains from registered domains.
Product update fix

More reliable website categorization evidence

  • Unreachable websites now keep the existing unreachable reason in API errors instead of returning an empty reason.
  • Interrupted page responses are rejected as incomplete evidence, while supported partial and cached fallback results continue to work.
Product update fix

Social username checker update

  • Earlier username-check behavior has been restored while fixes for response handling and international text are retained.
Product update fix

Clearer technology results during website outages

  • Fast technology scans now distinguish failed website connections and incomplete responses from empty pages.
  • After a failed fetch, fast scans can return a previously verified result, clearly marked as stale. Requests with skip_cache=1 continue to bypass saved results.
Product update fix

Fewer unknown results for larger social pages

  • Social username checks now return fewer unnecessary unknown results for larger pages, while malformed or blocked responses remain unknown.
  • Social username checks now preserve accented and non-Latin text when reading profile pages, instead of corrupting it.
Product update fix

Safer social username results

  • Social username checks handle unreadable responses more cautiously and keep uncertain results unknown.
  • YouTube checks continue using other available evidence during temporary limits. An empty channel lookup alone no longer marks a username available.
Product update fix

AI request-log analysis recovers from brief connection failures

  • AI analysis of request logs now retries once after a temporary connection failure within a bounded limit; requests that still fail remain errors.
Product update fix

More reliable scraping and WHOIS availability

  • Scrape requests now distinguish unreachable target sites from DomScan platform failures more reliably, reducing unnecessary 503 responses.
  • WHOIS and RDAP lookups are less likely to encounter transient availability errors during bursts of other checks.
  • Improved TLS deep-scan startup reliability during concurrent activity; transient failed starts are refunded.
Product update improvement

Threads username checks are more precise

  • Threads username checks now use exact validation when public profile evidence is inconclusive, reducing unknown results without treating blocked or changed responses as available.
Product update feature

Account admins for shared billing

  • Account owners can promote existing members to admins or return them to guest access from the Members page.
  • Admins can view billing, manage payment methods and auto-recharge, and purchase credits for the shared account without becoming its owner.
Product update fix

GitHub reserved usernames resolve correctly

  • GitHub username checks now distinguish unused but unavailable names from claimable names, so reserved routes are no longer reported as available.
Product update fix

Deleted Reddit usernames resolve correctly

  • Usernames from deleted Reddit accounts are now identified as unavailable because Reddit does not recycle them.
Product update improvement

Registrar pricing coverage now follows current evidence

  • Registrar coverage pages and sitemap links now reflect current successful standard-source evidence and configured exact-domain integrations.
  • Stale, quarantined, disabled, and metadata-only provider coverage is not published.
  • Published provider pages make their available standard-price and exact-domain scope clear.
Product update fix

More resilient social username checks

  • Facebook, Threads, and YouTube username checks now retry inconclusive public profile evidence before returning an unknown result.
  • Threads rate limits and login walls remain explicit unknown results and are never presented as available usernames.
Product update fix

MAC, website scan, and hosted-domain lookups are more resilient

  • MAC vendor lookups now recover from cold cache conditions and continue returning verified manufacturer data.
  • Website vulnerability scans now recover from temporary page-fetch transport failures within the request window.
  • WHOIS lookups for domains hosted under private platform suffixes now return limited DNS-backed evidence instead of an RDAP protocol error when registry data is not applicable.
Product update fix

IP lookups now return geolocation and network data reliably

  • Fixed an issue that could return every geolocation and network field as null. IP lookups now return available location, coordinates, ASN, and organization data with clear freshness and attribution metadata.
  • If IP intelligence is temporarily unavailable, the API now returns a retryable service-unavailable response and automatically refunds the request credit instead of returning a successful all-null result.
Product update feature

Agent Readiness scoring and expanded agent checks

  • Agent Readiness now provides a transparent 0-100 score across discoverability, content, access policy, and capabilities, with separate confidence and check-level evidence.
  • Expanded the audit to more than 35 bounded checks, including sitemaps, Markdown delivery, crawler policy, API catalogs, OAuth metadata, Agent Skills, WebMCP, remote MCP, and page structure.
  • Unknown evidence is excluded from scoring and lowers confidence. Emerging features are labeled by maturity, and the audit does not execute discovered tools or act as an SEO ranking.
  • Public HTML pages now support explicit `Accept: text/markdown` requests with `Vary: Accept` and canonical linkage, with a new Markdown sitemap and sanitized public agent guide for discovery.
Product update feature

DomScan API expands to the Postman API Network and prepares for Zyla

  • The DomScan Postman workspace is now publicly available with the complete collection aligned to the current OpenAPI contract.
  • A generated Zyla catalog with 106 marketplace-eligible operations, complete descriptions, examples, and provider-gateway authentication has been submitted for Zyla review.
  • The submitted Zyla surface excludes account-bound workflows. Availability on Zyla begins after marketplace approval.
  • The homepage footer now links to verified public DomScan listings on RapidAPI, Apify, and Postman.
Product update fix

Identity resolution now handles slow page lookups gracefully

  • Website fetching now stays within a bounded lookup window below the identity-resolution request deadline.
  • Unresolved single lookups return HTTP 200 with fetch_state: "unknown" and empty evidence, while bulk lookups return unknown data for affected items. Relevant credits are refunded.
Product update feature

Focused DomScan domain intelligence Actors for Apify

  • Added a focused Apify Actor catalog for WHOIS/RDAP, DNS, domain health, SSL, technology, reputation, subdomain, valuation, and availability checks.
  • Added structured per-target datasets and automation-ready outputs with explicit success and error status.
  • Added successful-result pricing by Actor, with failed results excluded from successful-result billing and Apify platform usage charged separately.
Product update fix

Email preferences now distinguish no choice from opting out

  • When an authentication flow did not show the optional email-guidance choice, it no longer records that missing choice as an explicit opt-out from onboarding or lifecycle emails.
  • We also repaired only affected accounts where the missing choice can be proven, while preserving any later dashboard preference changes and unsubscribes.
Product update improvement

RapidAPI catalog refreshed

  • RapidAPI subscribers can call supported stateless endpoints with their marketplace key and no separate DomScan account.
  • The catalog now includes 106 eligible operations with complete descriptions, request examples, and response examples for domscan.p.rapidapi.com.
  • Legacy endpoints and account-backed workflows were removed so the listing matches its executable capabilities.
  • Verified RapidAPI subscriber identities and plans now appear in the admin traffic report without storing marketplace API keys.
Product update feature

A full API playground in the dashboard

  • Browse and search every public API endpoint from one interactive dashboard workspace.
  • Build requests from the live API contract, edit JSON payloads, and run them with your signed-in session.
  • Inspect formatted responses, status, timing, credit details, and ready-to-copy cURL, JavaScript, and Python examples.
  • Open the API Playground directly from the signed-in sidebar, with active-page highlighting across desktop and mobile layouts.
  • Work in a dedicated full-page playground with stronger contrast, clearer focus states, and more room for requests, responses, and generated code.
  • Successful responses now replace the empty state correctly and use clearer, syntax-highlighted JSON on desktop and mobile.
Product update improvement

API docs sidebar navigation, clarified

  • Find endpoints faster with sticky search and actions that stay available while you browse.
  • Browse collapsible categories with item counts, clearer hierarchy, and stronger current-page highlighting.
  • Use the keyboard shortcut to focus search, with responsive layouts that keep navigation readable on smaller screens.
v2.15.0 feature

API v2.15.0: clearer responses and typed SDKs

  • API responses now include additive headers for request IDs, credits requested, charged, refunded, and remaining, rate-limit details, response time, API version, and data freshness. Existing response bodies are unchanged.
  • Errors now return a consistent, actionable shape with an error type, code, HTTP status, retry guidance, request ID, and a link to relevant documentation.
  • The interactive quickstart now remembers your preferred language and lets you run a real availability request with your API key, then shows response time, credits charged, and request ID.
  • The TypeScript and Python SDKs reach v0.3.0 with generated request and response types, full-response metadata, structured error classes, and safe retries that honor Retry-After and require idempotency keys for write retries.
Product update improvement

Privacy and cookie policies updated for product analytics

  • The cookie policy now documents the PostHog analytics cookie, what it stores and how long it lasts.
  • A new session replay section explains that recordings only run once you accept analytics cookies, that everything you type is masked, and that domains and email addresses are removed from page addresses and titles.
  • PostHog is listed as a subprocessor, with its purpose, the data it receives and its European Union storage region.
Product update improvement

More reliable social username checks

  • Exact present and missing-handle evidence is now used across more supported social, creator, and developer platforms.
  • Ambiguous, blocked, rate-limited, malformed, or identity-mismatched responses remain unknown instead of being presented as available.
  • Improved profile and channel redirect handling marks a name as taken only when the returned identity matches the requested handle.
Product update improvement

Safer, more consistent page checks

  • Scraping, technology detection, categorization, redirects, and public-page checks now share one bounded retrieval policy.
  • When primary retrieval capacity is temporarily unavailable, checks use a bounded backup path while preserving the same safety and result-classification rules.
  • Browser-rendered and non-rendered checks now use the same classification safeguards for blocked, rate-limited, and unreachable targets.
Product update improvement

Web page retrieval retry refinements

  • Existing resilient retries now use a different request profile after a retryable block or error from a permitted public page.
  • Rate-limited responses continue to skip retries.
Product update feature

Product discovery and navigation refresh

  • Organized the catalog around six product suites and solution-led discovery, so visitors can move from a goal to the relevant products and APIs.
  • Restored the interactive homepage with trust logos and a unified call to action for exploring products and getting started.
  • Unified docs navigation, corrected locale-safe links, and kept product section navigation visible on desktop.
  • Refined suite and solution pages with clearer action hierarchy, richer product and workflow cards, and responsive layouts that stay readable from desktop to mobile.
  • Rebuilt provider comparisons around current first-party pricing, real billing units, and workload-specific tradeoffs instead of generic placeholders.
  • Added a keyboard-friendly API finder to the homepage so visitors can search products by name, goal, input, or endpoint path and open the right API directly.
  • Added a site-wide command palette for fast keyboard search across products, API endpoints, documentation, suites, and free tools.
v2.14.0 feature

Evidence-First Vulnerability Intelligence

  • Added GET /v1/vulnerabilities with exact OSV package and version correlation plus deterministic web security configuration findings.
  • Added CISA KEV and FIRST EPSS prioritization, explicit unknown and partial coverage, and safe passive scanning without exploit payloads.
  • Published a localized scanner tool, dedicated API guide, developer documentation, MCP and SDK support, and standard or deep scan pricing.
v2.13.0 feature

Six New Bulk Data APIs

  • Added batch endpoints for subdomain discovery, Certificate Transparency, email authentication, hosting detection, RDAP, and DNS resolver comparison.
  • Each accepts up to 10 items, preserves input order, returns per-item errors, and charges the normal per-item rate.
  • Updated endpoint credit rates, including WHOIS at 3 credits per request or submitted bulk domain. Current rates are available at /v1/pricing.
v2.12.0 Breaking

Bulk Endpoint Credit Alignment

  • Bulk endpoints now bill the same per-item credits as individual requests across every plan.
  • Updated billing, pricing metadata, API docs, dashboard pricing, OpenAPI, Swagger, and Postman artifacts to use standard per-item bulk rates.
  • Bulk endpoints remain available for batching work into fewer requests with the same per-item credit cost.
v2.11.0 feature

API Guides & Pricing Refresh

  • Added a dedicated API pricing page with clearer endpoint pricing, billing links, and plan guidance
  • Localized API guide pages now share a unified layout with setup steps, examples, and next actions
  • Expanded API reference coverage so more public endpoints have dedicated guide pages instead of index-only listings
  • Improved MCP setup landing pages and developer actions across guide examples
  • Guide and docs pages now bypass stale page cache more aggressively so updates appear faster
v2.10.1 fix

Availability Confidence & ccTLD Fallbacks

  • Availability responses now include a `confidence` field to distinguish authoritative registry answers from heuristic fallbacks
  • Added DNS and WHOIS fallback handling for `.es` and similar registries that restrict direct availability checks
  • Fixed `skipCache` mode dropping results when RDAP fails mid-request
  • Improved handling for access-denied RDAP responses and transient registry dampening caches
v2.10.0 improvement

WHOIS Fallback Expansion

  • TLD validation now uses live IANA bootstrap data across all routes
  • Added WHOIS fallback for TLDs without RDAP bootstrap coverage and for registries with unreachable RDAP servers
  • Bulk status checks can now fall back to WHOIS for unsupported TLDs instead of failing early
  • WHOIS availability parsing now recognizes more multilingual registry responses
  • `/v1/ip` now returns HTTP 400 for private and reserved IP ranges instead of 500
v2.9.0 improvement

Data Quality & Performance Upgrades

  • Improved Spamhaus, tech detection, SSL, and reputation result quality across multiple intelligence endpoints
  • Expanded KV caching and unified resolver and timeout handling for lower-latency lookups
  • Improved bulk status error reporting and aligned OpenAPI auth examples with production behavior
  • Refreshed public docs and localized metadata across API landing pages
v2.8.0 feature

Website Categorization API Overhaul

  • Website categorization now uses an IAB-inspired taxonomy with multi-signal scoring
  • Responses include better-ranked categories, subcategories, and confidence scores
  • Added bulk categorization support and caching for larger analysis jobs
  • Docs and OpenAPI examples now reflect richer categorization responses and confidence thresholds
v2.7.0 fix

Historical Data Reliability

  • Expanded passive snapshot recording to strengthen `/v1/whois/history` and related historical views
  • Fixed missed history writes caused by background persistence timing on some routes
  • Historical tables now capture more consistent domain change data over time
  • Added D1 retry handling and bulk endpoint fixes for transient failures
v2.6.0 feature

Phase 4: New Capabilities & Data Enrichment

  • New `/v1/parking` endpoint - detect parked domains and aftermarket listings via DNS, redirect, and HTML analysis
  • New `/v1/whois/history` endpoint - track WHOIS changes over time with D1-backed snapshot storage
  • Threat intelligence now aggregates URLhaus + Spamhaus DBL + heuristic patterns
  • Domain valuation anchored to real market sale data with comparable categories
  • Hosting detection fetches dynamic IP ranges from AWS, GCP, and Cloudflare (cached 24h in KV)
  • SPF validation now counts recursive DNS lookups (RFC 7208 10-lookup limit)
  • Open Graph, Twitter Card, and meta tag extraction added to `/v1/tech`
  • DKIM checking expanded from 10 to about 50 selectors covering all major ESPs
  • DNS queries now fall back to Google DoH when Cloudflare is unavailable
  • Error cache uses type-specific TTLs for smarter retry behavior
  • Budget state is persisted so it survives application restarts
  • Added IPv6, security.txt, BIMI, MTA-STS, HTTPS/SVCB, domain age, and transfer_locked fields
v2.5.0 feature

Multi-currency Support

  • Added GBP and JPY currency support for domain valuation
  • New `currency` parameter on `/v1/value` endpoint (default: USD)
  • Valuation responses now include `currency` field
v2.4.2 improvement

Mobile Experience Improvements

  • Fixed mobile navigation UI issues
  • Added floating navigation menu for API docs on mobile
  • Improved terminal component responsive behavior
v2.4.1 security

Security Hardening

  • Enhanced input validation across all endpoints
  • Added rate limiting protection for authentication endpoints
  • Improved XSS protection on user-generated content
  • Security headers now enforced on all responses
v2.3.0 feature

Reverse Lookup APIs

  • New `/v1/reverse/mx` endpoint - find domains by mail server
  • New `/v1/reverse/ip` endpoint - find domains hosted on an IP
  • Both endpoints support pagination via `offset` and `limit` params
  • Results include confidence scores and last-seen timestamps
v2.2.1 fix

RDAP Reliability Improvements

  • Fixed intermittent timeouts with certain ccTLD registries
  • Improved retry logic for rate-limited RDAP servers
  • Better handling of malformed RDAP responses
  • Cache now respects registry-specific TTL hints
v2.2.0 feature

Email Authentication API

  • New `/v1/email-auth` endpoint for email security auditing
  • Validates SPF, DKIM, and DMARC configurations
  • Returns actionable recommendations for misconfigured records
  • Includes deliverability score based on authentication setup
v2.1.0 Breaking

Response Format Standardization

  • BREAKING: Error responses now use consistent `error.code` and `error.message` format
  • BREAKING: Removed deprecated `err` field from all responses
  • BREAKING: HTTP 429 responses now include `retry_after` in seconds (was milliseconds)
  • Added `error.suggestion` field with actionable guidance
  • All timestamps now in ISO 8601 format
Migration Example
// Before (v2.0.x)
{ "err": "rate limited", "retry": 5000 }

// After (v2.1.0+)
{
  "error": {
    "code": "RATE_LIMITED",
    "message": "Too many requests",
    "suggestion": "Reduce request frequency or upgrade plan",
    "retry_after": 5
  }
}
v2.0.3 fix

Bulk Endpoint Stability

  • Fixed race condition in bulk status checks causing duplicate results
  • Improved memory efficiency for large bulk requests
  • Added request deduplication for identical domains in same batch
v2.0.2 improvement

Performance Optimizations

  • Reduced average response time by 35% through edge caching improvements
  • Optimized DNS resolution with connection pooling
  • Bootstrap data now refreshed in background without blocking requests
v2.0.1 fix

IDN Domain Handling

  • Fixed punycode conversion for internationalized domain names
  • Improved validation for mixed-script domain labels
  • Added support for new gTLDs with non-ASCII characters
v2.0.0 Breaking

API v2 Launch

  • BREAKING: All endpoints moved from `/api/` to `/v1/` prefix
  • BREAKING: Authentication now requires API key in `X-API-Key` header (was query param)
  • BREAKING: Rate limits now per-key instead of per-IP for authenticated requests
  • New domain availability engine with 40% faster lookups
  • Added support for 400+ new TLDs
  • Introduced credit-based pricing model
  • New dashboard for API key management
Migration Example
// Before (v1.x)
GET /api/check?domain=example.com&key=xxx

// After (v2.0+)
GET /v1/status?name=example&tlds=com
Headers: X-API-Key: xxx
v1.5.0 feature

Tech Stack Detection

  • New `/v1/tech` endpoint for website technology detection
  • Identifies CDN providers, CMS platforms, frameworks, and analytics tools
  • Detection based on HTTP headers, HTML patterns, and JavaScript fingerprints
v1.4.0 feature

Domain Health Checker

  • New `/v1/health` endpoint for comprehensive domain health checks
  • Validates DNS configuration, SSL certificates, and security headers
  • Added `/v1/health/quick` for lightweight checks (DNS only)
  • Health scores now included in domain profile responses
v1.3.2 fix

Certificate Transparency Improvements

  • Fixed pagination for domains with 1000+ certificates
  • Added wildcard certificate detection
  • Improved certificate parsing for non-standard issuers
v1.3.1 deprecation

Deprecation Notice

  • Deprecated: `/api/*` endpoints will be removed in v2.0 (September(2025)
  • Deprecated: Query parameter authentication (`?key=xxx`) will be removed in v2.0
  • Added deprecation warnings in response headers for affected endpoints
  • Migration guide available at /docs#migration-v2
v1.3.0 feature

Typosquatting Detection

  • New `/v1/typos` endpoint for brand protection
  • Detects keyboard-based typos, homoglyph attacks, and TLD variations
  • Threat scoring based on registration status and content similarity
  • Webhook notifications for newly registered typosquatting domains

Get Notified of Breaking Changes

Subscribe to receive email alerts before we ship breaking changes.