Endpoint

B

netintel.dev/dns-propagation/check

· score 77/100 · recomputed 34m ago

Query a domain's DNS record across 10 geographically distributed public resolvers simultaneously — returns what each resolver sees, whether results are consistent, propagation percentage, and a readiness score so agents can confirm DNS changes have fully propagated globally.

NEW_UNKNOWN
First seen
5d ago
Probes stored
3

Score

B
77 of 100
recomputed 34m 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
3h ago 402 161 ms exact
eip155:8453
0xdaDc…b9Df 0.030000 clean
4d ago 402 192 ms exact
eip155:8453
0xdaDc…b9Df 0.030000 clean
4d ago 402 252 ms exact
eip155:8453
0xdaDc…b9Df 0.030000 clean

Reference

URLhttps://netintel.dev/dns-propagation/check
Sourceswell-known
Recipient per catalogue0xdaDc335482AD545296Fd7b28518A251fFCbEb9Df
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.