hubvibe-io.com
https://hubvibe-io.com/audit/securityShares a payout wallet with 70 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Security headers check for a website: audits HTTPS, HSTS, Content- Security-Policy (CSP), X-Content-Type-Options, X-Frame-Options / clickjacking protection, Referrer-Policy and CORS from the real HTTP response of any live URL. Findings with severity for what is missing. Header posture only, not a penetration test.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 31ms · p95 34msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 10/20/2026, 12:00:00 AM | 100% | 5 | 29ms |
| 10/21/2026, 12:00:00 AM | 100% | 10 | 31ms |
| 10/22/2026, 12:00:00 AM | 100% | 1 | 30ms |
| 10/23/2026, 12:00:00 AM | 100% | 1 | 30ms |
| 10/24/2026, 12:00:00 AM | 100% | 1 | 27ms |
| 10/25/2026, 12:00:00 AM | 100% | 1 | 33ms |
| 10/27/2026, 12:00:00 AM | 100% | 1 | 73ms |
| 10/29/2026, 12:00:00 AM | 100% | 1 | 29ms |
| 10/31/2026, 12:00:00 AM | 100% | 1 | 26ms |
| 11/2/2026, 12:00:00 AM | 100% | 1 | 31ms |
| 11/5/2026, 12:00:00 AM | 100% | 1 | 31ms |
| 11/7/2026, 12:00:00 AM | 100% | 1 | 34ms |
| 11/9/2026, 12:00:00 AM | 100% | 1 | 32ms |
| 11/12/2026, 12:00:00 AM | 100% | 1 | 32ms |
| 11/14/2026, 12:00:00 AM | 100% | 1 | 26ms |
| 11/16/2026, 12:00:00 AM | 100% | 1 | 29ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 67
- Activity
- 2
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 58% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- HOSTINGER operations, UAB
- Domain registered
- 2026-09-03
- Hosting network
- HOSTINGER-HOSTING
- Hosting country
- US
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 11/18/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 10/20/2026 | 21 | 3.15 | 1 |
| 10/21/2026 | 29 | 4.35 | 2 |
| 10/22/2026 | 16 | 2.4 | 1 |
| 10/23/2026 | 37 | 4.47 | 2 |
| 10/24/2026 | 23 | 3.45 | 1 |
| 10/25/2026 | 16 | 2.2 | 1 |
| 10/26/2026 | 21 | 6 | 2 |
| 10/27/2026 | 19 | 2.85 | 1 |
| 10/28/2026 | 21 | 3.15 | 1 |
| 10/29/2026 | 27 | 4 | 2 |
| 10/30/2026 | 39 | 6.15 | 1 |
| 10/31/2026 | 33 | 5.2 | 1 |
| 11/1/2026 | 41 | 6.9 | 1 |
| 11/2/2026 | 35 | 5.85 | 2 |
| 11/3/2026 | 25 | 3.65 | 3 |
| 11/4/2026 | 17 | 2.8 | 1 |
| 11/5/2026 | 43 | 6.9 | 1 |
| 11/6/2026 | 31 | 5.05 | 1 |
| 11/7/2026 | 28 | 4.25 | 1 |
| 11/8/2026 | 11 | 1.55 | 1 |
| 11/9/2026 | 5 | 0.7 | 1 |
| 11/10/2026 | 16 | 1.9 | 2 |
| 11/11/2026 | 11 | 1.15 | 1 |
| 11/12/2026 | 8 | 0.75 | 1 |
| 11/13/2026 | 1 | 0.05 | 1 |
| 11/14/2026 | 1 | 0.1 | 1 |
| 11/16/2026 | 3 | 0.3 | 2 |
| 11/17/2026 | 12 | 1.45 | 1 |
| 11/18/2026 | 2 | 0.5 | 1 |
This payout wallet is shared: figures cover all 71 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.
Response schema
{
"$ref": "#/components/schemas/Response200_d506ad1e"
}