Domain Intelligence
Inspect DNS records, mail configuration, SPF, DMARC, nameservers, TLS availability, HTTP status, and basic server information.
Query domains, inspect infrastructure and build network intelligence directly into your applications. No dashboard archaeology required.
Small, focused APIs for inspecting the systems that sit between users and applications.
Inspect DNS records, mail configuration, SPF, DMARC, nameservers, TLS availability, HTTP status, and basic server information.
ASN, network ownership, routing information, prefixes, and IP intelligence.
Inspect URLs, redirects, TLS configuration, response information, and security signals.
Send a real request to the Domain Intelligence API and inspect the raw response.
curl -X POST https://api.sharperr.dev/v1/domain \
-H "Content-Type: application/json" \
-d '{"domain":"cloudflare.com"}'
Use the API from whatever stack you're already using. Because apparently every developer needs three ways to make an HTTP request.
curl -X POST "https://api.sharperr.dev/v1/domain" \
-H "Content-Type: application/json" \
-d '{"domain":"example.com"}'
const response = await fetch(
"https://api.sharperr.dev/v1/domain",
{
method: "POST",
headers: {
"Content-Type": "application/json"
},
body: JSON.stringify({
domain: "example.com"
})
}
);
const data = await response.json();
console.log(data);
import requests
response = requests.post(
"https://api.sharperr.dev/v1/domain",
json={
"domain": "example.com"
}
)
print(response.json())
The API is intentionally small while the underlying infrastructure is being built.
sharperr.dev ........ operational Domain API ......... operational Network API ........ in progress URL API ............ in progress Control plane ...... in progress
{
"service": "api.sharperr.dev",
"status": "operational",
"version": "v1",
"endpoints": {
"domain": "available",
"network": "in_progress",
"url": "in_progress"
}
}
Infrastructure should be programmable, inspectable and boring in exactly the right ways.
api.sharperr.dev ↗