Endpoint

B

agent.connskill.com/v1/exposure-check

· score 77/100 · recomputed 1h ago

Leak and infostealer exposure of a domain: employee and user credentials seen in stealer logs (with last-seen dates and malware families), leak records mentioning the domain, and official breaches - aggregates only, never passwords or personal records

NEW_UNKNOWN
First seen
16h ago
Probes stored
3

Score

B
77 of 100
recomputed 1h ago

The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.

We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.

Recent probes

WhenCodeLatencyScheme and network RecipientPriceFindings
1h ago 402 18 ms exact
eip155:8453
0x43B8…63dE 0.030000 clean
9h ago 402 21 ms exact
eip155:8453
0x43B8…63dE 0.030000 clean
16h ago 402 22 ms exact
eip155:8453
0x43B8…63dE 0.030000 clean

Reference

URLhttps://agent.connskill.com/v1/exposure-check
Sourceswell-known
Recipient per catalogue0x43B85AE58f0A2505c710Bc715d6f3EB16b1f63dE
Machine access/v1/endpoint · /full · badge

Is this your endpoint?

The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.

We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.

Next

Market overview →

Payments, median ticket, who pays whom, who settles.

Wallets →

Payers, recipients and facilitators, listed separately.

Facilitators →

Who actually settles — including those in no public registry.

API →

Verdict before payment, seller and wallet scores, market aggregates.