SAMPLE PROBE · metmuseum.org

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 metmuseum.org 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 metmuseum.orgor 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: 429
STACK: unknown
TLS_DAYS_LEFT: UNKNOWN
FINAL_HOST: metmuseum.org
GENERATED_UTC: 2026-10-29 18:15

SAMPLE STRIP · metmuseum.org▸ rendered

Your agency - Website Care Snapshot

Reachability

HTTP429

ResponseUNKNOWN ms

Redirectedno

Certificate

RenewsUNKNOWN

Days LeftUNKNOWN

FlagUNKNOWN

DNS

A Records1A record(s)

wwwresolves

Security headers

strict-transport-securityMISSINGMISSING

content-security-policyMISSINGMISSING

x-frame-optionsMISSINGMISSING

Hardening opportunities: strict-transport-security MISSING, content-security-policy MISSING, x-frame-options MISSING, 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 metmuseum.orgor 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 metmuseum.org. 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.