November 2026
Nov 18
No more false HTTP/3 changes. HTTP/3 and HTTP/2 are detected from a per-connection response header that a site can send on one visit and not the next, so they flipped between checks with nothing actually changing. They still appear in scan results, but they are no longer reported as "added" or "removed" in history, the change feed, webhooks or watch alerts, and past entries of this kind have been removed.
Nov 18
Block answers are free. When a site answers our scanner with a challenge, rate limit, access-denied or server-error page (HTTP 202, 401, 403, 429 or 5xx), the call no longer counts toward your DetectZeStack monthly limit on /analyze, /check, /vulnerability, /analyze/batch and /compare. The response carries an X-Site-Blocked header with the site's status code; /compare and /vulnerability also return site_blocked, /compare leaves such sites out of shared/unique, and /vulnerability skips the CVE lookup for them. Also fixed: cached /vulnerability calls are now free, as cached calls on the other endpoints already were.
Nov 18
Watch health on the dashboard. Each watch now shows whether it is OK, being refused by the site, retrying, or paused, in plain words. Paused watches get a Resume button, and resuming gives the watch a fresh 5 checks. The /watches API returns the same information in new status and status_detail fields.
Nov 18
Watches no longer switched off by a single block. If a watched site answers our scanner with access-denied or a server error (HTTP 401, 403 or 5xx), the check is skipped and retried at the next scheduled time instead of disabling the watch immediately. A watch is only switched off, with an email explaining why, after 5 failed checks in a row. Missing pages (404/410) still disable the watch straight away.
Nov 18
Block pages no longer recorded as a site's stack. When a site answers our scanner with a challenge, rate limit, access-denied or server-error page (HTTP 202, 401, 403, 429 or 5xx), the scan is still returned to you as before, but it is no longer saved to the domain's history, used for change detection, sent to webhooks, or shown on public tech pages (older entries recorded this way were removed on Nov 18, along with the false changes they caused). This prevents false "technology removed/added" changes when a site briefly blocks us.
Nov 18
More Tag Manager tags recognised. With include=gtm, /analyze now also reports Reddit Ads, Quora Pixel, Crazy Egg and AdRoll when they are configured in a site's Google Tag Manager container. Without the parameter, responses are unchanged.
Nov 18
Optional: tags configured in Google Tag Manager. Add include=gtm to /analyze to also get the marketing and analytics tags a site has configured in its Google Tag Manager container, such as Google Ads, Google Analytics, Facebook Pixel, LinkedIn Insight Tag or HubSpot. Many of these load only through Tag Manager, so a plain page scan can't see them. Each one carries an evidence field naming the container and tag. They are configured tags, so a tag may not fire on every page. Combine with DNS records as include=dns_records,gtm. Without the parameter, responses are exactly as before.
Nov 18
Optional: company tools from DNS records. Add include=dns_records to /analyze to also get the technologies a company's DNS reveals: its mail provider (for example Google Workspace or Microsoft 365), the services it sends email through (for example Sendgrid or Amazon SES) and SaaS tools it has verified its domain with (for example Stripe or Atlassian Cloud). Each one is marked source: dns with an evidence field naming the record. These describe the company rather than the web page. Without the parameter, responses are exactly as before.
Nov 17
Batch and compare no longer count failed or cached URLs. /analyze/batch and /compare used to count every URL in the request toward your monthly limit. Now only URLs we actually scan count: URLs that failed and URLs answered from the 24-hour cache are given back, and X-RateLimit-Used shows the corrected count. A call still needs room for all its URLs when it starts. This applies to your DetectZeStack monthly limit; nothing else about your plan changes.
Nov 17
First seen and last seen dates on every technology. Each technology in /analyze now includes first_seen and last_seen: the first and most recent time DetectZeStack detected it on that domain. A new first_scanned field shows when we first detected anything on the domain, so a technology first seen after that date was added while we were watching, and one with the same date was already there. These are our own sightings, not the date the site adopted the tool, and a later date can also mean our detection learned to recognise it then. For technologies a site has removed, use /changes. These fields are new additions; nothing existing was changed or removed.
Nov 14
More accurate detection of analytics, ads, chat and framework tags. /analyze now finds tags that load through a short inline script rather than a plain script file, including Google Analytics 4 and Google Ads, Facebook Pixel, Microsoft Clarity, Hotjar, Crisp, Intercom, PostHog and Tawk.to, plus Next.js, Astro, Webflow, Firebase, Supabase and Google Fonts on more sites. Three wrong answers are fixed: sites behind Cloudflare no longer show “Google Cloud” hosting because of Cloudflare’s certificate, Rewardful affiliate tags no longer show as ClickBank, and LiteSpeed Cache and All in One SEO no longer appear twice. Response format is unchanged; expect more technologies per site.
Nov 14
Updated detection fingerprints and security patches. The detection engine now uses the latest fingerprint release, which adds Google Ads conversion tracking, so /analyze may return a few more technologies for the same site. The server also moved to the current Go release with all published security fixes applied. No changes to request or response formats.
September 2026
Sep 10
Watches now follow your API key when you rotate it. Rotating a key from the dashboard left any watches attached to the old key behind: they stopped being scanned and disappeared from the dashboard, so they could not be edited or removed. Watches now move to the new key as part of the rotation, and existing watches that were stranded this way have been reattached to your current key. If you had a watch go quiet after rotating, it resumes on its next scheduled scan.
Sep 10
Payment-failure notices for direct subscribers are working again. A change in how Stripe formats invoice events meant failed and successful payment events were being recorded but not acted on, so the “action needed” email after repeated card failures could not be sent. The events are parsed correctly now. Your subscription status and access were never affected by this; only the courtesy email was missing.
Sep 2
Cached responses no longer count against your rate limit. Re-analyzing a domain already scanned within the 24-hour cache window is now free on every plan — the credit is refunded automatically and the X-RateLimit-Used header reflects it. This is what the plan description has always promised; until now the request was billed anyway. No action needed, and nothing was charged retroactively that shouldn’t have been — the change applies from today forward.
Sep 2
Repeat lookups of a domain that redirects now hit the cache. A request for example.com that redirected to www.example.com was stored under the redirected hostname but looked up under the one you sent, so it missed the cache every time. Those lookups were re-scanning the target on every call and paying full latency. They are now served from cache on the second request, like every other domain.
Sep 2
Rate-limit and plan-gate responses now link to the right place. If you subscribe directly, the
upgrade_url in a
429 and the
upgrade field in a
403 now point to your account’s checkout at
detectzestack.com/pricing instead of the RapidAPI marketplace. RapidAPI subscribers continue to be directed to the RapidAPI listing. Three of those links also pointed at a URL that rendered a blank page; that is fixed.
Sep 2
Webhook delivery logs now record only the hostname of your callback URL, never the full path or query string. If you embed a token in your webhook URL, it is no longer written to our logs.
June 2026
Jun 4
Failed scans no longer cost credits. If /analyze (or any of /check, /lookup, /dns, /vulnerability, /history, /stats, /changes, /certificate/check, /security) returns a 4xx or 5xx because the target domain didn’t resolve, the TLS handshake failed, the fetch timed out, or the site was unreachable, the credit it consumed is now refunded automatically. The X-RateLimit-Used header reflects the refund. Customers whose monthly counter was charged for failed scans in early June were credited retroactively. The /site, /analyze/batch, and /compare endpoints have separate refund handling on the roadmap.
May 2026
May 25
Dashboard now shows an upgrade prompt when free-tier usage hits 80% of the monthly quota — one click to Pro, Ultra, or Mega via Stripe Checkout. Free-tier users no longer hit the cap silently.
May 25
Returning users on the dashboard can now paste their saved key into the “Try in browser” widget. Previously the button silently 409’d if you came back after revealing your key once (we don’t store plaintexts — peppered hash only).
May 25
Magic-link sign-in emails now include a sample curl command and an explanation of what to expect on the dashboard. First-time users know what to do with their key the moment they land.
May 25
Blog posts auto-link the first mention of named technologies (Cloudflare, Next.js, React, Stripe, etc.) to /built-with/{Tech} — click any tech name in a post to see which sites use it.
May 25
/tech/{domain} pages with thin or unreliable detection data (fewer than 4 technologies, fewer than 2 categories, or a non-2xx scan response) now return X-Robots-Tag: noindex. Improves the signal-to-noise ratio of the indexed corpus.
May 25
/built-with/{Tech} URLs are now case-normalized via 301 to the canonical case — e.g. /built-with/cloudflare 301s to /built-with/Cloudflare.
May 25
WhatRuns URL cluster consolidated: /whatruns-api-docs and /blog/whatruns-alternative-api now 301 to the canonical /blog/whatruns-api-key-alternative.
May 18
Resend added as an alternative outbound-email transport. Magic-link, activation, and webhook-alert emails are delivered via Resend (preferred) or Gmail SMTP as a fallback.
May 18
Re-engagement email cron added: paid customers who haven’t made an API call in 14 days get a once-daily nudge with a magic-link refresh, until they re-engage or unsubscribe.
May 18
Dashboard Quick start card adds a “Try in browser” button — one click runs /analyze?url=stripe.com against your key and renders the JSON response inline. No terminal needed for the first call.
May 18
OpenAPI spec updated to include the /check, /lookup, /vulnerability, and /site endpoints (previously documented only in the RapidAPI portal).
May 17
DNS signature catalog grew from 111 to 132 CNAME fingerprints — more accurate provider detection on Vercel, Statsig, Fastly, Sentry, Mailgun, and 17 other services.
May 17
New blog post:
Slack Webhook Setup Guide — how to wire up Slack alerts on the Watches (tech-change-alerts) feature.
May 11
Direct billing via Stripe shipped. Sign up at /signup with your email — magic-link verification, then pick a plan and pay via Stripe Checkout. No RapidAPI account required.
March 2026
Mar 31
Added DNS Intelligence endpoint (/dns) — query A, AAAA, CNAME, MX, TXT, NS records with automatic provider fingerprinting (111 CNAME signatures).
Mar 31
Added SSL/TLS Certificate Check endpoint (/certificate/check) — inspect certificate issuer, expiry, chain, protocol version, and SANs for any domain.
Mar 31
Added Security Headers endpoint (/security) — grades websites A+ through F on CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy.
Mar 22
Added technology change feed (/changes) — track when monitored domains add, remove, or update technologies. Webhook alerts on changes.
Mar 13
Chrome extension published to Chrome Web Store — one-click tech stack detection in browser.
Mar 7
Added usage warnings — API responses include a warning when you reach 80% of your monthly quota.
Mar 4
Added /tech/{domain} pages — browse any domain's tech stack directly on detectzestack.com.
February 2026
Feb 25
Custom domain live at detectzestack.com (migrated from detectzestack.fly.dev).
Feb 14
Added /analyze/batch — analyze up to 10 URLs in a single API request with optional CSV export.
Feb 14
Added /compare — side-by-side tech stack comparison across 2–10 sites.
Feb 14
Added /webhooks — HMAC-signed webhook notifications when domains are analyzed.
Feb 14
Added /history and /stats — view past scans and per-key usage analytics.
Feb 11
DetectZeStack API launched on RapidAPI with 7,300+ technology signatures via HTTP fingerprinting, DNS CNAME analysis, TLS certificate inspection, and custom header matching.