Endpoint

B

api.ozdreamtools.de/api/robots/lint

robots.txt Linter (RFC 9309) · score 77/100 · recomputed 15h ago

Lints and validates a caller-supplied robots.txt against RFC 9309 and reports every check, not only the failures: group structure, product token charset, path patterns, special characters, other records, size limit. Given a user agent and URLs it recomputes the allow/disallow decision per URL, naming the winning rule, its octet length and the tiebreak that applied. Where the RFC is silent or contradicts itself, the reading used is stated. Makes no outbound request.

NEW_UNKNOWN
First seen
6d ago
Probes stored
4

Score

B
77 of 100
recomputed 15h 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
22h ago 402 36 ms exact
eip155:8453
0x4Dd5…C1Dc 0.050000 clean
1d ago 402 79 ms exact
eip155:8453
0x4Dd5…C1Dc 0.050000 clean
5d ago 402 21 ms exact
eip155:8453
0x4Dd5…C1Dc 0.050000 clean
5d ago 402 18 ms exact
eip155:8453
0x4Dd5…C1Dc 0.050000 clean

Reference

URLhttps://api.ozdreamtools.de/api/robots/lint
Sourcesbazaar
Recipient per catalogue0x4Dd5E59475A55f1C2c0816469600663cb74cC1Dc
Price per catalogue0.050000
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.