What TechDash sends over the network
Review website fetches, TechDash services, Google APIs, webhooks, and optional crash uploads.
Last checked 1 September 2026
TechDash stores crawl history locally, but features that contact websites or external services still make outbound requests. Each destination can see the request from this computer and may apply its own logging and retention policy.
Use hostnames and feature categories for firewall or proxy rules. TechDash does not promise fixed IP addresses for TechDash services, Google, Slack, Microsoft, Discord, monitored websites, content-delivery networks, DNS, or domain-registration services. Their providers can change addresses without an app update.
Customer-usable destination list
Allow only the categories required for the features you use:
- TechDash licensing, updates, installer downloads, and optional crash reports: HTTPS to
api.techdash.com. - Google sign-in: HTTPS to
accounts.google.com. - Google token exchange: HTTPS to
oauth2.googleapis.com. - Google Search Console properties and Search Analytics: HTTPS to
www.googleapis.com. - Google URL Inspection: HTTPS to
searchconsole.googleapis.com. - Slack webhooks: HTTPS to
hooks.slack.com. - Discord webhooks: HTTPS to
discord.com,discordapp.com, or a subdomain ofdiscord.com. - Microsoft Teams webhooks: HTTPS to
webhook.office.com, a subdomain ofwebhook.office.com, a subdomain oflogic.azure.com, or a subdomain ofapi.powerplatform.com. - Connectivity checks: HTTP to
captive.apple.comand, as a fallback,www.msftconnecttest.com. - Website monitoring: the monitored origins and destinations loaded or checked from those pages.
A local development build can use administrator-configured replacement service URLs. The list above describes packaged production behavior.
Website monitoring traffic
TechDash requests monitored pages and renders them locally. Enabled checks can also request links, images, redirects, robots.txt, sitemaps, llms.txt, favicon and manifest files, certificates, DNS records, and domain-registration services. A rendered page can contact third-party scripts, fonts, images, analytics, consent tools, and content-delivery networks just as it would in a normal browser.
The destination can receive this computer's public IP address, requested URL, timing, request headers, and selected or custom user agent. Basic Authentication credentials are sent only when you saved them for that website and the request is eligible to use them.
Because page dependencies and lookup providers vary, there is no complete static host list for monitoring. Blocking an asset or third-party destination can change the rendered page or cause a specific check to fail.
TechDash license and update services
License requests to api.techdash.com include the normalized license email, license key, app version, local device ID, activation or unlinking state, platform, architecture, and computer hostname. A successfully activated app normally revalidates once a day when a stable connection is available.
Update checks to the same host include the current version, platform, architecture, packaged channel, license email and key, and device ID. Linux also identifies the required package type. Eligible installers are downloaded from short-lived authorized URLs on api.techdash.com.
These requests do not attach the crawl database, stored HTML, screenshots, or website data directory.
Google Search Console
Google sign-in opens accounts.google.com. TechDash exchanges and refreshes tokens through oauth2.googleapis.com, reads properties and Search Analytics through www.googleapis.com, and sends URL Inspection requests to searchconsole.googleapis.com.
Requests include the connected Google authorization, Search Console property, date range, dimensions, queries, pages, or inspected URL required for the action. Deleting a website removes its local connection data but does not erase data held by Google or revoke the Google account grant.
Webhooks and crash reports
When you configure a supported webhook, TechDash sends test, incident, and recovery text to the saved provider URL. That provider receives the message content and source request. Keep webhook URLs private.
When Settings > Privacy > Send crash reports is On, a packaged app can send a compact crash report to api.techdash.com. It includes technical app and platform details and can contain limited memory fragments such as URLs or error text. It does not attach the TechDash database as a file.
Desktop notifications stay on the computer. Sharing an incident opens the chosen external service with prepared text, which is not sent until you continue in that service.
Your network review is complete when the features you use can reach their hostname categories and you have not created rules that depend on permanent provider IP addresses.