FleetOpus
WHITE-LABEL · FOR AGENCIES

A white-label website report your client can verify without you.

You finalise the report. Your client gets an opaque share link and verifies the bytes themselves — no account, no login, no trust required. Every report is sealed with a SHA-256 chain and the public verifier walks it end-to-end. The shell below is a live, anonymous probe of a public site. When your agency drops its own brand on top, the seal still says what we measured and when — it just says it in your voice.

GENERATESEALVERIFYYOUR BRAND ON TOP
HTTP_STATUS
200
STACK
unknown
TLS_DAYS_LEFT
UNKNOWN
FINAL_HOST
www.airbnb.com
GENERATED_UTC
2026-10-29 18:16
SHELL · www.airbnb.com▸ live probe
Your agency - Website Care Snapshot

Your agency

Website Care Snapshot

www.airbnb.com 2026-10-29 18:16

This is a point-in-time public check of www.airbnb.com generated from one public probe.

Reachability

HTTP200
ResponseUNKNOWN ms
Redirectedyes to www.airbnb.com

Certificate

RenewsUNKNOWN
Days LeftUNKNOWN
FlagUNKNOWN

DNS

A Records2A record(s)
wwwskipped (already www)

Security headers

strict-transport-securityPRESENTmax-age=63072000; includeSubDomains; preload
content-security-policyMISSINGMISSING
x-frame-optionsPRESENTSAMEORIGIN

Hardening opportunities: content-security-policy MISSING, x-content-type-options not nosniff, referrer-policy MISSING

Stack

unknown
Prepared by Your agency · point-in-time snapshot generated 2026-10-29 18:16 Powered by FleetOpus
WHAT CHANGES UNDER YOUR BRAND

The seal stays ours. The voice becomes yours.

White-label is more than a logo swap. Below is what an agency actually controls on a FleetOpus shell, and what an agency does not control — because the things the agency cannot touch are exactly the things the client is verifying.

YOU CONTROL
  • Logo, wordmark, and cover-letter tone.
  • Section ordering, itemised maintenance log.
  • Color tokens for the shell chrome (the “flight strip” paper).
  • Incident narrative — the agency writes the language, the agency owns the wording.
  • Which probe targets get sent monthly and which get summarised.
WE HOLD FIXED
  • The SHA-256 chain. No agency role can silently edit after the seal.
  • The verifier. The client's link walks the chain end-to-end.
  • Probe provenance — generated_utc, final_host, vantage.
  • The UNKNOWN gate — a slot the probe cannot measure does not become a guess.
  • No login. No portal. No password reset email. The share link is the contract.
WHY AGENCIES BUY THIS

It answers the question a retainer cannot.

Most retainer churn is not about price. It is about the client quietly asking, six months in, “what did we actually pay for last month?” A white-label report that the client can verify is the only honest answer to that question. The seal is what makes it survive scrutiny.

  • Defensible against the client's finance team.
  • Defensible against your own future staff turnover.
  • Defensible against an audit, a litigation hold, or a successor agency.
  • Cheaper than a custom portal by an order of magnitude.
HOW THE SEAL WORKS
  1. 1. Generate — the monitoring engine drafts the report body on the agency side.
  2. 2. Review — the agency edits the cover letter, the incident narrative, the maintenance log.
  3. 3. Finalise — the agency clicks Finalise. The bytes are sealed: a SHA-256 chain is computed over the canonical form.
  4. 4. Share — the agency gets an opaque share link and forwards it. No login.
  5. 5. Verify — the client opens the link. The public verifier walks the chain end-to-end. Any silent edit breaks the seal.
SHAPE · HOW IT FITS YOUR AGENCY

Built for 5–50 person web shops on retainer.

FleetOpus fits the agency that already runs monthly retainers for clients and is tired of writing the same report from scratch. We do not sell to the client; the agency stays the relationship owner. Pricing scales with the number of sealed reports, not the number of seats.

SHAPE 01

Per-client, not per-seat

One client relationship = one report stream. Your project managers, account leads, and tech directors all see the same sealed bytes; nobody is locked out by a missing seat licence.

SHAPE 02

Anonymous probe, branded surface

The probe runs against your client's apex domain from a published vantage. The branded surface is your logo, your colour tokens, your tone. The vantage never becomes anonymous to your client — it is named in the report.

SHAPE 03

Opaque share, public verify

The share link is opaque but the verifier is public. Your client can hand the link to their auditor, their board, or their lawyer, and the chain still walks.

NEXT STEP

Probe your client's domain. See the shell your agency would brand.

Type any apex domain at /sample. One probe, one shell, one honest answer. If the shape works for your retainers, request early access on the waitlist and we will be in touch with a sealed-report pilot setup.

Probe a domain →← back to the chart
HONESTY · WHAT THIS PAGE IS NOT

What we are not saying.

  • We are not auditing airbnb.comor its owners. The numbers above come from one public probe of the apex — that's all.
  • The shell is a draft of what your agency's report would look like. The agency writes the language; the seal is what the client trusts.
  • A result of UNKNOWNmeans the probe could not measure it from our vantage point — not that the property is broken or absent.