$ fitfo identify
>_FITFO
Find Infrastructure, Tech & Footprint Overview for client website handoffs.
Scan a domain, map ownership and launch risks, and turn public signals into a first-call plan.
$ fitfo onboard clientdomain.com
>domainregistrar: Namecheap / expires: 2026-03-14OK
>dnsns: Cloudflare / proxy: activeOK
>hostingplatform: WP Engine / cms: WordPress 6.4OK
>emailspf: pass / dkim: pass / dmarc: quarantineWARN
>analyticsga4: active / gtm: found / fbpx: noneOK
1 risk / 2 unknowns / Markdown note ready
> what fitfo maps
One domain in.Full infrastructure map out.
> report modes
Four depths of discovery.
Each mode builds on the last. Start light, go deep when the project demands it.
$ fitfo snapshot
Snapshot
Light first-call walkthrough. Quick domain scan, surface-level infrastructure, and enough context to ask better questions.
$ fitfo brief
Brief
Deeper prep and research packet. Full DNS enumeration, hosting analysis, email safety checks, and analytics inventory.
$ fitfo plan
Plan
Current-state to future-state build plan with architectural decisions, redirect strategy, launch checklist, and rollback markers.
$ fitfo onboard
Onboard
Full wrapper for a new client. Deep scan, research, Wayback, architecture and launch planning, and a saved Markdown onboarding note.
> architectural state map
Redesigns are not blank slates.
Every client site has existing URLs, subdomains, forms, tracking, and traffic patterns that must be intentionally kept, reworked, deprecated, or redirected.
Current State Assessment
Map URLs, subdomains, DNS, forms, integrations, posts, and cataloged risks.
Architectural Decisions
Decide what to keep, rework, merge, redirect, deprecate, or monitor.
Redesign Phase Handling
Track risks during the build so launch is planned instead of improvised.
Launch & Post-Launch
Confirm redirects, monitor canonical signals, and keep rollback paths clear.
> why it matters
Every line is a launch risk you almost missed.
Lost DNS / email access
Client does not know who holds the registrar login, and MX records get moved by accident.
Hidden Cloudflare ownership
A proxy layer lives outside the client account and masks the origin server.
Broken lead forms
Contact forms hit an endpoint nobody remembered during the redesign.
Missed subdomains
Staging, portal, shop, or app subdomains break when nameservers change.
App/review redirect mistakes
Booking, canonical host, or review links are not accounted for.
Lost local SEO equity
Service pages, city landing pages, and citation URLs change without a redirect map.
> install / run
Core commands. Markdown-first output.
FITFO is currently a private repo. Public release is planned after validation.
# link the cli locally
npm link
# verify environment
fitfo doctor
# quick scan with deep flag
fitfo snapshot example.com --deep
# build plan with research signals
fitfo plan example.com --deep --search --location "City, ST"
# full onboarding wrapper
fitfo onboard example.com> status
Where FITFO stands today.
Private-first
Current repo remains private while real client workflows are validated.
GPL-2.0-or-later
Licensed for WordPress-friendly distribution when ready.
Dependency-free mode
Core scan runs without heavy crawler dependencies.
Future-driven detection
Architecture supports richer integrations without expanding the V1 surface.