SAMPLE PROBE · amazon.com

A real care-report shell, filled from a live public probe.

We did one HTTP request, one TLS handshake, one DNS lookup, one www check, and a header sniff against amazon.com and rendered the result through the same shell your agency would use to send its own client's monthly report. No claim is made about amazon.comor its owners — any site on the public internet is eligible for a shell like this. Slots we couldn't measure appear as UNKNOWN, never a guess.

Your agency can send this monthly. Probe your client's domain →← back to the chart

HTTP_STATUS: 200
STACK: unknown
TLS_DAYS_LEFT: UNKNOWN
FINAL_HOST: www.amazon.com
GENERATED_UTC: 2026-10-29 18:12

SAMPLE STRIP · www.amazon.com▸ rendered

Your agency - Website Care Snapshot

Reachability

HTTP200

ResponseUNKNOWN ms

Redirectedyes to www.amazon.com

Certificate

RenewsUNKNOWN

Days LeftUNKNOWN

FlagUNKNOWN

DNS

A Records3A record(s)

wwwskipped (already www)

Security headers

strict-transport-securityPRESENTmax-age=47474747; includeSubDomains; preload

content-security-policyPRESENTupgrade-insecure-requests;report-uri https://metrics.media-amazon.com/

x-frame-optionsPRESENTSAMEORIGIN

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

Stack

unknown

HONESTY · WHAT THIS PAGE IS NOT

What we are not saying.

We are not auditing amazon.comor its owners. The numbers above come from one public probe of the apex — that's all.
We are not claiming any relationship between FleetOpus and amazon.com. Any site on the public internet will yield a shell like this.
A result of UNKNOWNmeans the probe could not measure it from our vantage point — not that the property is broken or absent.
The shell is a draft of what your agency's report could look like. Your agency writes the report; your client can verify it.