Frequently Asked Questions
Common questions about using Teste.no.
General
How often does Teste.no scan my site?
Each test has its own schedule — ranging from every 4 hours (performance, security) to weekly (deep crawl, AI analysis). Uptime monitoring runs every 60 seconds. You can also trigger any test manually at any time.
Will the scans slow down my website?
Tests are staggered by weight class and use polite crawling practices (configurable delays between requests). The adaptive throttle automatically backs off if your server signals rate limiting. Heavy tests run with low concurrency (default: 3 concurrent requests).
Can I pause all testing temporarily?
Yes. Enable the Kill Switch in Settings → Team Config → Runs & Scheduling. This blocks all scheduled and manual test runs for your entire team. You can also set up maintenance windows for individual targets.
Findings & Alerts
Why did a finding disappear?
Findings auto-resolve when the next scan no longer detects the issue. Resolved findings remain in history but no longer affect your target status or trigger alerts.
Can I ignore a finding I don't care about?
Yes — use the Mutebutton on any finding. You can mute by fingerprint (this specific issue), by test (all findings from that test), or by test + target (this test on this site only). Muted findings don't affect status or trigger notifications.
Why did a finding's severity increase?
Dynamic severity escalation automatically promotes findings that persist. A WARNING finding that recurs 15+ times or stays open for 14+ days escalates to CRITICAL. This is configurable in team and target settings.
Uptime
How quickly will I know if my site goes down?
With the default configuration (3 consecutive failures required), you'll be alerted within approximately 3 minutes of actual downtime. Immediate retries catch transient blips without waiting for the next cycle.
What is keyword verification?
An optional feature where you specify a word that must appear in your page body. If the word is missing — even if the server returns HTTP 200 — the site is marked DOWN. This catches database errors, maintenance pages, and CDN failures that still return a 200 status.
SEO & AI
How does AI enrichment work?
When enabled, findings are sent to OpenAI for contextual analysis. The AI generates a business-impact summary and step-by-step fix recommendation tailored to your specific technology stack. Results are cached globally — identical issue types across sites reuse the same recommendations.
What is the AI spending cap?
You can set a monthly USD limit on AI usage in Settings → Team Config → AI Usage. When the cap is reached, AI enrichment pauses (or warns, depending on your setting). In-app notifications and email alerts inform you when the cap is hit.
Integration
Can I use Teste.no in my CI/CD pipeline?
Yes. The CLI tool (npx @teste-no/teste-cli scan URL --token tno_xxx --json) returns exit codes 0/1/2 for pass/warning/fail, making it suitable for CI gates.
Does Teste.no work with AI coding assistants?
Yes. The MCP (Model Context Protocol) server lets AI tools like Cursor and Claude Desktop interact directly with your monitoring data — list targets, check findings, trigger scans, and manage incidents through natural language.