Create your QuietFox account
This account clears every scan QuietFox runs on your behalf — one login, full history, one place to see what was tested.
You'll be the account Admin. You can invite your IT contractor as a Member later.
This is a work-in-progress prototype, not a public build. Enter the test credentials to continue.
This account clears every scan QuietFox runs on your behalf — one login, full history, one place to see what was tested.
You'll be the account Admin. You can invite your IT contractor as a Member later.
Setup status
You're already in — finish these whenever works for you. Nothing you've done so far is lost, and nothing expires.
Not yet cleared to scan.
Dashboard
Here's where things stand for fernwooddental.com.
Account setup
We only scan targets you've proven you own. Add a DNS record or a small file to your site — takes about two minutes.
fernwooddental.com — not yet verified
fernwooddental.com resolves through Cloudflare's shared network. Basic-mode tests run normally — findings about network-level infrastructure reflect Cloudflare's edge, not servers you exclusively control. Aggressive-mode network tests that could affect shared infrastructure are automatically restricted, regardless of approval status.
Most registrars apply this within minutes. Already added it? Check now.
Account setup
This is the legal step that makes active testing lawful — you're confirming you have the authority to allow it, on the record.
Plain-language summary: you're giving QuietFox permission to run the Basic-mode tests you select against fernwooddental.com, on a schedule you control. You can revoke this at any time, which stops all future scans immediately.
This document is an AI-assisted starting draft and has not yet been reviewed by a licensed attorney. It is shown here so you can see the actual shape of the flow — not as a finished legal agreement.
Account setup
Active security testing carries real risk, so every account is manually reviewed before it can run a scan. Upload your current cyber or general liability policy.
Scans
Run a one-off scan anytime, or set up recurring testing so you never have to remember.
One-time or recurring — monthly, quarterly, semi-annual, or annual — each with its own tests selected.
Canceled scans are kept here — nothing is deleted, and you can restore any of them.
| Date | Mode | Trigger | Tests | Findings | Status | Report |
|---|
Basic mode is what we recommend for almost every account. You control exactly which checks run below.
A one-time scan runs once on this date, then moves straight to your scan history — no recurring commitment.
Passive checks and safe, non-destructive active tests. Won't modify or disrupt anything on your site.
Recommended · selectedBroader, exploitation-style testing for teams that need deeper validation.
Finds every public subdomain and web endpoint tied to your domain, so nothing gets tested blind.
Read-only. Just maps what's already publicly visible — never touches your systems.
Checks which network ports respond on your target, the way someone would "jiggle the doors."
Passive probing only — never attempts to log in or exploit anything found open.
Identifies the exact software and version behind each open port — turns "something's listening" into "Apache 2.4.41."
Read-only service identification — never attempts to log in or exploit anything found.
Finds hidden pages and files search engines don't know about.
Runs thousands of community-maintained checks for known security flaws and common setup mistakes.
Non-destructive detection only — flags issues without attempting to exploit them.
Deeper infrastructure-level scanning beyond web-facing services.
Crawls your site like a visitor would, checking for common web weaknesses.
Uses passive and safe active checks only — no data-altering requests.
Tests forms and search fields for a common flaw that could expose your database.
Detection-only mode — confirms a flaw exists without extracting or changing any data.
Additional web scanners layered on top of the baseline scan.
Tests pages behind a login, using credentials you provide.
Extends testing to REST and GraphQL API endpoints.
Checks that your site's HTTPS setup uses strong, up-to-date encryption.
Read-only connection tests — never modifies anything on your server.
Attempts to actually exploit a finding to confirm real-world impact.
Checks cloud storage and container configurations for exposure.
You're only charged once the scan actually completes — a failed or aborted run costs you nothing.
No one at QuietFox is watching this scan live — it's running fully automated, end to end.
Findings
7 tests completed · 6 findings · scanned Aug 17, 2026. Raw scan data was discarded after this report was generated.
Reports
Every completed scan generates a report — download the certificate for your records, or for whoever asked you to run this.
Team
Everyone who can see scans, findings, and reports for fernwooddental.com.
| Name | Role | Status |
|---|
Admin manages billing and team; Member runs and configures scans; Read-only can view findings and reports.
Billing
Your payment method and scan billing history.
| Date | Description | Amount | Status |
|---|
Every organization on QuietFox. Set up or trigger a scan on their behalf, or pull their results — anything you do shows up in their own portal.
| Organization | Status | Plan | Last / next scan |
|---|
Accounts waiting on domain-ownership edge cases or insurance-document review before they can scan.
| Organization | Domain verification | Insurance document | Submitted | Action |
|---|
Set up or trigger a scan for this customer, or pull their results. Anything you do here shows up in their own portal, tagged as set up by QuietFox Support.
| Date | Mode | Trigger | Tests | Findings | Status | Report |
|---|