DDashy

Public tools

Run a focused check before you commit it to a dashboard.

Use the public tools to inspect a target, confirm the signal is useful, then save the checks into Dashy when you need history, alerts, and a shared status page.

5
domain and DNS scanners
5
website health scanners
6
SEO, API, and dependency scanners
Check now Run a focused public scanner
Create board Send the same target into quick start
Share safely Public dashboard and display view are live first
Keep it Save to scheduled monitoring when it matters

Scan boundaries

Public tools stay useful without becoming intrusive.

Public targets
Checks use public URLs, DNS, certificates, headers, sitemaps, robots.txt, and status feeds.
No privileged probing
Dashy avoids login bypass, vulnerability scanning, port sweeps, and destructive tests.
Dashboard path
Useful findings move into quick-start boards, scheduled checks, alerts, and display tiles.

Recommendation boundary

Free scans return evidence before recommendations.

Evidence first
Public tools show the observed status, dates, DNS records, headers, routes, and safe summaries before any commercial suggestion.
Owner review
Affiliate, referral, registrar, DNS, hosting, CDN, or security-service suggestions stay inside owner-controlled workspace views until enabled.
Public output
Public dashboards, status pages, display views, and white-label client links do not show partner recommendations by default.

Choose by outcome

Start with the problem, then run the matching public check.

Start here

Scan a domain, then decide what deserves monitoring.

Most users begin with a domain scan because it finds the ownership, DNS, SSL, and routing signals that often become the first dashboard checks.

Certificate
Issuer, expiry date, and days remaining.
DNS
A, AAAA, MX, TXT, and nameserver records.
Routing
Final URL, response status, and public dashboard fit.
  1. 1Run a scanCheck one public target without signing in.
  2. 2Create a boardSend the same target into quick start.
  3. 3Keep historySchedule checks, alerts, and display tiles.

What gets monitored

Public scans map directly to scheduled dashboard components.

Domain pack
Domain expiry, DNS records, nameserver drift, email DNS, CAA, DNSSEC, and SSL days remaining.
Website pack
Uptime, redirects, content match, security headers, Core Web Vitals, sitemap, and robots.txt checks.
API and dependencies
JSON contracts, vendor status summaries, Search Console visibility, and GA4 traffic snapshots.

Recommended bundles

Run the checks that match the job in front of you.

Create from quick start
Launch check Before a site or app goes live

Confirm SSL days, DNS, uptime, redirects, headers, sitemap, robots.txt, and Core Web Vitals before sharing the URL.

Agency intake First pass for a client website

Collect domain ownership, expiry, email DNS, security posture, sitemap health, and public-page availability in one client-safe path.

API and vendor watch For integrations customers depend on

Check public JSON contracts, dependency status feeds, redirects, and uptime before turning vendor health into a scheduled board.

Save checks, history, and alerts in Dashy.

Turn a one-off public scan into scheduled checks with retention, alerting, and shareable dashboard views.

  1. 1Scan onceUse a focused public checker before creating an account.
  2. 2Schedule itKeep history, alerts, and expiry warnings.
  3. 3Share safelyPublish status pages or display tiles from saved boards.
Create dashboard

Domain and DNS

Ownership, routing, and domain posture

Website health

Availability, redirects, content, and performance

SEO, APIs, and dependencies

Search hygiene and integration health