risk data for machine payments
Endpoint
netintel.dev/typosquat/scan
Generate common typo and look-alike variations of a domain and check which are already registered — catches character swaps, omissions, additions, homoglyphs, and alternate TLDs so agents can detect typosquatting and brand-impersonation domains targeting a company.
Score
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
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 15m ago | 402 | 153 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.050000 | clean |
| 7h ago | 402 | 159 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.050000 | clean |
| 4d ago | 402 | 195 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.050000 | clean |
| 4d ago | 402 | 226 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.050000 | clean |
Reference
| URL | https://netintel.dev/typosquat/scan |
| Sources | well-known |
| Recipient per catalogue | 0xdaDc335482AD545296Fd7b28518A251fFCbEb9Df |
| 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.